Triple
T2202230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Task Force One |
E50515
|
entity |
| Predicate | usedTargetType |
P35851
|
FINISHED |
| Object | decommissioned warships |
—
|
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: decommissioned warships | Statement: [Joint Task Force One, usedTargetType, decommissioned warships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTargetType Context triple: [Joint Task Force One, usedTargetType, decommissioned warships]
-
A.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
B.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
C.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
D.
notableTargetType
chosen
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
E.
usesStandardType
Indicates that one entity employs or relies on a predefined, commonly accepted standard type defined elsewhere.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa33f0881908403604eafb73ecf |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.