Triple
T13784031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Niagara |
E331206
|
entity |
| Predicate | FrenchCastleConstructionDate |
P52046
|
FINISHED |
| Object | 1726 |
—
|
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: 1726 | Statement: [Fort Niagara, FrenchCastleConstructionDate, 1726]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrenchCastleConstructionDate Context triple: [Fort Niagara, FrenchCastleConstructionDate, 1726]
-
A.
originalCastleFoundedIn
Indicates the specific year or time period when the original version of a castle was first established or built.
-
B.
castleBuilt
chosen
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
C.
originalCastleFoundedBy
Indicates that an original castle was established or created by a specific person, group, or authority.
-
D.
dateOfFortification
Indicates the specific date or time period when a structure or site was fortified or had defensive works constructed or significantly strengthened.
-
E.
eraOfMainCastle
Indicates the historical period or era during which the main castle associated with an entity was built, used, or most prominent.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0247ccc881908dad7b547221f15d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.