Triple
T6815418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of St. Trophime |
E156739
|
entity |
| Predicate | mainPortalDate |
P73232
|
FINISHED |
| Object | late 12th century |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: late 12th century | Statement: [Church of St. Trophime, mainPortalDate, late 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPortalDate Context triple: [Church of St. Trophime, mainPortalDate, late 12th century]
-
A.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
B.
admissionDate
Indicates the date on which an entity (such as a person, application, or item) is formally admitted, accepted, or entered into a system or institution.
-
C.
integratedDate
Indicates the date on which one entity was incorporated, combined, or brought into a larger system or whole.
-
D.
visionDate
Indicates the date on which a particular vision, plan, or conceptual idea was created, recorded, or formally established.
-
E.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c68828b26c819090fe9df7612bbc27 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d32dc19c8190a871cc1ff1471a58 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:17 p.m.