Triple
T26117503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Saint-Germain-en-Laye (1632) |
E658861
|
entity |
| Predicate | restoredControlOf |
P28512
|
FINISHED |
| Object | New France |
—
|
NE NERFINISHED |
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: New France | Statement: [Treaty of Saint-Germain-en-Laye (1632), restoredControlOf, New France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredControlOf Context triple: [Treaty of Saint-Germain-en-Laye (1632), restoredControlOf, New France]
-
A.
redefinedControlOver
Indicates that an entity has newly established or significantly altered authority, influence, or decision-making power over another entity or process.
-
B.
restoredRight
Indicates that a previously lost, removed, or suspended right has been returned to its holder.
-
C.
restoredAsOwnerOf
chosen
Indicates that an entity has been reinstated or returned to its previous status as the owner 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.
transferredControlFrom
Indicates that authority or control over something has been moved or handed over from one entity to another.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60ac96f64819094e4d02dfc5f46b1 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:06 p.m.