Triple
T26628443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château d'Anet |
E668423
|
entity |
| Predicate | laterRestoredIn |
P98133
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Château d'Anet, laterRestoredIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRestoredIn Context triple: [Château d'Anet, laterRestoredIn, 19th century]
-
A.
laterRestored
Indicates that something previously altered, damaged, or removed was subsequently brought back to its earlier state or condition.
-
B.
wasRestoredAt
chosen
Indicates that an entity was brought back to a previous or improved state at a specific time or place.
-
C.
restoredBy
Indicates that an entity has been returned to a previous or improved state through the actions or intervention of another entity.
-
D.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
-
E.
temporarilyRestored
Indicates that a previously unavailable or altered state, condition, or connection has been brought back to its former status for a limited or non-permanent period.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 27, 2026, 2:24 a.m.