Triple
T29617641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combined Task Force 152 |
E754903
|
entity |
| Predicate | hasTaskForceNumber |
P75856
|
FINISHED |
| Object | 152 |
—
|
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: 152 | Statement: [Combined Task Force 152, hasTaskForceNumber, 152]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTaskForceNumber Context triple: [Combined Task Force 152, hasTaskForceNumber, 152]
-
A.
isNumberedTaskForceOf
Indicates that one entity is a specifically numbered task force that is organizationally part of, or assigned to, another entity.
-
B.
taskForceNumber
chosen
Indicates the numerical identifier assigned to a specific task force within a larger organizational or operational context.
-
C.
taskForce
Indicates a collaborative relationship in which multiple entities are formally grouped to work together as a specialized team on a specific task or mission.
-
D.
hasForceInterventionBrigade
Indicates that an entity includes or is supported by a designated force intervention brigade as part of its operational structure or mission.
-
E.
commandingForceSize
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 6:32 p.m.