Triple
T23539418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Bridger State Historic Site |
E577696
|
entity |
| Predicate | inceptionAsFort |
P152726
|
FINISHED |
| Object | 1843 |
—
|
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: 1843 | Statement: [Fort Bridger State Historic Site, inceptionAsFort, 1843]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionAsFort Context triple: [Fort Bridger State Historic Site, inceptionAsFort, 1843]
-
A.
inception
Indicates the point in time or event at which something begins, originates, or is first established.
-
B.
inceptionAsSymbol
Indicates that one entity begins to function or be recognized as a symbolic representation or emblem of another entity.
-
C.
inceptionPart
Indicates that one entity represents a component, segment, or phase within the initial creation or starting process of another entity.
-
D.
inceptionAsMemorial
Indicates that something was originally created, founded, or established specifically to serve as a memorial or commemoration.
-
E.
inceptionCentury
Indicates the century during which something (such as an institution, tradition, or practice) was originally founded or began.
- F. None of above. chosen
Provenance (4 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1a66b88190811b38523ea606fe |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:10 p.m.