Triple
T2040482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Task Force 17 |
E44731
|
entity |
| Predicate | roleAtBattleOfTheCoralSea |
P28183
|
FINISHED |
| Object | U.S. carrier striking force |
—
|
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: U.S. carrier striking force | Statement: [Task Force 17, roleAtBattleOfTheCoralSea, U.S. carrier striking force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtBattleOfTheCoralSea Context triple: [Task Force 17, roleAtBattleOfTheCoralSea, U.S. carrier striking force]
-
A.
roleAtPearlHarbor
Indicates the specific role, position, or function an entity held in relation to the events at Pearl Harbor.
-
B.
worldWarIIRole
Indicates the specific role, position, or function an entity had in relation to World War II.
-
C.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
D.
roleInKoreanWar
Indicates the specific function, position, or involvement an entity had during the Korean War.
-
E.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.