Triple
T32033460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château d’Asnières |
E818029
|
entity |
| Predicate | hasConstructionEnd |
P204241
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Château d’Asnières, hasConstructionEnd, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstructionEnd Context triple: [Château d’Asnières, hasConstructionEnd, 18th century]
-
A.
hasEndConstruction
Indicates that an entity is associated with, or terminates in, a specific construction or structural element at its end.
-
B.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
C.
hasConstructionEndYear
Indicates the year in which the construction of an entity was completed.
-
D.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
E.
typicalConstructionEnd
Indicates the usual or expected point in time or stage at which a construction process or building project is completed.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a03544239d4819087b6c232d6804977 |
completed | May 12, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_6a0353d685688190b01df77fc2f62bf2 |
completed | May 12, 2026, 4:22 p.m. |
| PDg | Predicate description generation | batch_6a03544190608190aa659147c9956a3c |
completed | May 12, 2026, 4:24 p.m. |
Created at: May 1, 2026, 12:18 a.m.