Triple
T37831356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Johnston (DD-821) |
E943210
|
entity |
| Predicate | namedAfterBattle |
P63
|
FINISHED |
| Object | Battle off Samar |
—
|
NE NERFINISHED |
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: Battle off Samar | Statement: [USS Johnston (DD-821), namedAfterBattle, Battle off Samar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterBattle Context triple: [USS Johnston (DD-821), namedAfterBattle, Battle off Samar]
-
A.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
C.
namedAfterTrophy
Indicates that one entity has been given a name derived from or in honor of a particular trophy.
-
D.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
E.
namedAfterLeague
Indicates that one entity has been given a name derived from or in honor of a particular league.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:19 p.m.