Triple
T750521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Eastern Solomons |
E15436
|
entity |
| Predicate | primaryForces |
P18776
|
FINISHED |
| Object | aircraft 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: aircraft carriers | Statement: [Battle of the Eastern Solomons, primaryForces, aircraft carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryForces Context triple: [Battle of the Eastern Solomons, primaryForces, aircraft carriers]
-
A.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
B.
primarySense
Indicates that one sense or meaning of an entity is designated as its main or most central sense among possible alternatives.
-
C.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
D.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
E.
primaryTraction
Indicates that one entity serves as the main source or means of traction, pulling power, or driving force for another entity or process.
- F. None of above. chosen
Provenance (4 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a58c0a84819094f07658dc651b36 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.