Triple
T7556024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Task Force |
E178667
|
entity |
| Predicate | isFormedFor |
P77594
|
FINISHED |
| Object | specific contingency |
—
|
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: specific contingency | Statement: [Joint Task Force, isFormedFor, specific contingency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormedFor Context triple: [Joint Task Force, isFormedFor, specific contingency]
-
A.
hasFormed
Indicates that an entity has come together or been created into a particular structure, group, or configuration.
-
B.
containsFormation
Indicates that one entity spatially or structurally includes or encloses a formation as part of its extent or composition.
-
C.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
D.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
E.
isFormalizedBy
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
- F. None of above. chosen
Provenance (4 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8d9ebe48190a08110695ce1eb55 |
completed | March 27, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f59517648190ac0a9e9cba045dd5 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:49 p.m.