Triple
T11574907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Johnston (DD-557) |
E274477
|
entity |
| Predicate | roleAtBattleOffSamar |
P28183
|
FINISHED |
| Object | screening destroyer for escort carriers |
—
|
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: screening destroyer for escort carriers | Statement: [USS Johnston (DD-557), roleAtBattleOffSamar, screening destroyer for escort carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtBattleOffSamar Context triple: [USS Johnston (DD-557), roleAtBattleOffSamar, screening destroyer for escort carriers]
-
A.
roleAtLeyteGulf
Indicates the specific role or function an entity performed in the context of the Battle of Leyte Gulf.
-
B.
roleAtGuadalcanal
Indicates the specific role, position, or function an entity held in relation to the Battle of Guadalcanal.
-
C.
roleAtBattleOfMidway
Indicates the specific role, position, or function an entity held or performed during the Battle of Midway.
-
D.
roleAtPearlHarbor
Indicates the specific role, position, or function an entity held in relation to the events at Pearl Harbor.
-
E.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89048120c81908258f984711f7dd4 |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.