Triple
T24293172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Planning and Execution Community |
E605879
|
entity |
| Predicate | includesStakeholderType |
P34203
|
FINISHED |
| Object | combatant commands |
—
|
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: combatant commands | Statement: [Joint Planning and Execution Community, includesStakeholderType, combatant commands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesStakeholderType Context triple: [Joint Planning and Execution Community, includesStakeholderType, combatant commands]
-
A.
hasStakeholderType
chosen
Indicates that an entity is associated with a stakeholder and specifies the category or role that stakeholder fulfills in relation to the entity.
-
B.
hasStakeholder
Indicates that an entity is a stakeholder of another entity, typically having an interest, involvement, or influence in its activities or outcomes.
-
C.
supportsParticipantType
Indicates that an entity is compatible with, or designed to work with, a specified type or category of participant.
-
D.
includesTeamType
Indicates that an entity encompasses or is associated with one or more specific categories or types of teams.
-
E.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f29157840c81908da157e93ad21527 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.