Triple
T6937863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arcul de Triumf |
E160597
|
entity |
| Predicate | previousStructureDate |
P59253
|
FINISHED |
| Object | wooden arch built in 1878 |
—
|
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: wooden arch built in 1878 | Statement: [Arcul de Triumf, previousStructureDate, wooden arch built in 1878]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousStructureDate Context triple: [Arcul de Triumf, previousStructureDate, wooden arch built in 1878]
-
A.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
B.
previousHolderStartDate
Indicates the date on which the immediately preceding holder of something (e.g., a position, title, or asset) began their tenure or ownership.
-
C.
preDates
Indicates that one entity existed, occurred, or was established earlier in time than another entity.
-
D.
predecessorBuildingDate
chosen
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
E.
currentStructureDatesToCentury
Indicates that the existing structure was originally built or last fundamentally constructed in the specified century.
- F. None of above.
Provenance (3 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.