Triple
T37837564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John C. Butler-class |
E943377
|
entity |
| Predicate | roleInBattleOffSamar |
P28183
|
FINISHED |
| Object | screening 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 escort carriers | Statement: [John C. Butler-class, roleInBattleOffSamar, screening escort carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOffSamar Context triple: [John C. Butler-class, roleInBattleOffSamar, screening escort carriers]
-
A.
opponentAtBattleOffSamar
Indicates that one entity served as an opposing force to another during the Battle off Samar.
-
B.
opponentCommanderAtBattleOffSamar
Indicates that one commander served as the opposing (enemy) commander to another during the Battle off Samar.
-
C.
roleInBattleOfSanCarlos
Indicates the specific role or participation an entity had in the Battle of San Carlos.
-
D.
roleAtLeyteGulf
Indicates the specific role or function an entity performed in the context of the Battle of Leyte Gulf.
-
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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a030713bd2881908bcc69e7d1e9fd09 |
completed | May 12, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a0304c29abc819085ffd17ab9a8c844 |
completed | May 12, 2026, 10:45 a.m. |
Created at: May 3, 2026, 4:19 p.m.