Triple
T25452483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daleville, Alabama |
E637822
|
entity |
| Predicate | formerlyKnownNearbyInstallationAs |
P40327
|
FINISHED |
| Object | Fort Rucker |
—
|
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: Fort Rucker | Statement: [Daleville, Alabama, formerlyKnownNearbyInstallationAs, Fort Rucker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyKnownNearbyInstallationAs Context triple: [Daleville, Alabama, formerlyKnownNearbyInstallationAs, Fort Rucker]
-
A.
hasNearbyInstallation
Indicates that one entity has another installation or facility located close to it in physical space.
-
B.
associatedInstallation
Indicates a relationship where one entity is linked to, or occurs in connection with, a particular installation (such as a facility, system, or setup) with which it is contextually or functionally related.
-
C.
installedNear
Indicates that one entity is installed in physical proximity to another entity, typically within a short, functionally relevant distance.
-
D.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
-
E.
formerNameOfContainedInstallation
chosen
Indicates that an installation previously had a different name while remaining the same contained installation.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 21, 2026, 2:03 p.m.