Triple
T6094789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Washington (BB-56) |
E135849
|
entity |
| Predicate | escortRole |
P33337
|
FINISHED |
| Object | fast carrier task forces |
—
|
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: fast carrier task forces | Statement: [USS Washington (BB-56), escortRole, fast carrier task forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escortRole Context triple: [USS Washington (BB-56), escortRole, fast carrier task forces]
-
A.
escortDuties
Indicates that one entity is responsible for accompanying and ensuring the safe or guided movement of another entity from one place or situation to another.
-
B.
escortDuty
chosen
Indicates that one entity is responsible for accompanying and protecting another entity during travel or movement.
-
C.
specialRole
Indicates that an entity holds a distinctive or exceptional function, status, or responsibility in relation to another entity or context.
-
D.
encodingRole
Indicates the role or function an entity has in the process of encoding information into a particular form or representation.
-
E.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a963bac8190bc0c33fef187875c |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.