Triple
T6372576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Air Force detachment |
E143385
|
entity |
| Predicate | canBeLocatedAt |
P28981
|
FINISHED |
| Object | joint base |
—
|
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: joint base | Statement: [United States Air Force detachment, canBeLocatedAt, joint base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeLocatedAt Context triple: [United States Air Force detachment, canBeLocatedAt, joint base]
-
A.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
B.
possibleLocation
chosen
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
E.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06829d76c819092b476631459233a |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.