Triple
T7341006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Regent |
E169245
|
entity |
| Predicate | militaryUseEndDate |
P14594
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Fort Regent, militaryUseEndDate, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryUseEndDate Context triple: [Fort Regent, militaryUseEndDate, 20th century]
-
A.
militaryUseEnd
chosen
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
-
B.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
C.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
D.
endOfWeaponsProduction
Indicates that the production or manufacturing of weapons has ceased or been brought to an end.
-
E.
hasMilitaryServiceEnd
Indicates the date or point in time at which an entity’s period of military service concludes.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:04 p.m.