Triple
T34281005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Smith National Historic Site |
E879588
|
entity |
| Predicate | originalFortEstablished |
P78331
|
FINISHED |
| Object | 1817 |
—
|
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: 1817 | Statement: [Fort Smith National Historic Site, originalFortEstablished, 1817]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalFortEstablished Context triple: [Fort Smith National Historic Site, originalFortEstablished, 1817]
-
A.
fortressOriginallyBuiltBy
Indicates that a particular fortress was initially constructed by a specified builder or group.
-
B.
fortressBuiltAs
Indicates that a fortress was originally constructed to serve as a particular type, role, or function.
-
C.
constructionBeganAsFortressIn
Indicates that the construction of something originally began with the purpose or function of serving as a fortress at a specified time or in a specified place.
-
D.
fortressBuiltUnder
Indicates that one structure or location was constructed directly beneath or within the protective area of a fortress.
-
E.
dateOfFortification
chosen
Indicates the specific date or time period when a structure or site was fortified or had defensive works constructed or significantly strengthened.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:57 a.m.