Triple
T27884128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GRK |
E705175
|
entity |
| Predicate | isJointUseWith |
P2507
|
FINISHED |
| Object | Fort Cavazos military air operations |
—
|
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: Fort Cavazos military air operations | Statement: [GRK, isJointUseWith, Fort Cavazos military air operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJointUseWith Context triple: [GRK, isJointUseWith, Fort Cavazos military air operations]
-
A.
isJointBase
Indicates that two or more components share a common base or foundation point.
-
B.
isSharedBy
chosen
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
C.
providesServicesJointlyWith
Indicates that two or more entities collaborate to offer services together as a joint provision rather than independently.
-
D.
mayBeManagedJointlyWith
Indicates that an entity can be administered, controlled, or overseen together with another entity as part of a shared or coordinated management arrangement.
-
E.
isHeldInConjunctionWith
Indicates that one event, activity, or occurrence takes place together with another at the same time or as part of a combined arrangement.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f639afdc6c819082f1c8a47bbbb93c |
completed | May 2, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:32 p.m.