Triple
T20749376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. military component commands |
E510676
|
entity |
| Predicate | existsInContextOf |
P118237
|
FINISHED |
| Object | joint 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: joint operations | Statement: [U.S. military component commands, existsInContextOf, joint operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existsInContextOf Context triple: [U.S. military component commands, existsInContextOf, joint operations]
-
A.
appearsInContextWith
chosen
Indicates that two entities are observed or used together within the same situational, textual, or usage context.
-
B.
namedInContextOf
Indicates that an entity is mentioned or identified specifically within a particular context, situation, or frame of reference.
-
C.
isKnownInContextOf
Indicates that an entity is recognized, relevant, or has significance specifically within a given context or domain.
-
D.
isRaisedInContextOf
Indicates that an entity is brought up, discussed, or introduced within a particular situational, thematic, or conversational context.
-
E.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c228af288190a20829d45c034c24 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:34 p.m.