Triple
T24981271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Johnson, Louisiana |
E625172
|
entity |
| Predicate | isHomeStationOf |
P105426
|
FINISHED |
| Object | Joint Readiness Training Center |
—
|
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: Joint Readiness Training Center | Statement: [Fort Johnson, Louisiana, isHomeStationOf, Joint Readiness Training Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHomeStationOf Context triple: [Fort Johnson, Louisiana, isHomeStationOf, Joint Readiness Training Center]
-
A.
hasStationAt
chosen
Indicates that an entity maintains or operates a station located at a specified place.
-
B.
ownedStation
Indicates that one entity possesses ownership or control over a particular station.
-
C.
isLocalStationFor
Indicates that a station serves a specific local area or locality as its primary service point.
-
D.
isLocalStation
Indicates that a station operates primarily within a limited local area or serves as a stop on a local (rather than regional or long-distance) service.
-
E.
hasStationNear
Indicates that one entity has a station located in close proximity to another entity.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:02 a.m.