Triple
T32033459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château d’Asnières |
E818029
|
entity |
| Predicate | hasConstructionStart |
P106367
|
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, hasConstructionStart, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstructionStart Context triple: [Château d’Asnières, hasConstructionStart, 18th century]
-
A.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
B.
hasEndConstruction
Indicates that an entity is associated with, or terminates in, a specific construction or structural element at its end.
-
C.
startOfConstructionApprox
chosen
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
-
D.
startConstruction
Indicates that an entity initiates the process of building or constructing another entity or structure.
-
E.
constructionStartedBy
Indicates that the construction of something was initiated or begun by a particular agent or entity.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0353887e848190ad98ecbbe7bbc061 |
completed | May 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_6a0352dfb5648190b9f8c9b7c388d2a1 |
completed | May 12, 2026, 4:18 p.m. |
Created at: May 1, 2026, 12:18 a.m.