Triple
T16444511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montana-class battleship |
E399389
|
entity |
| Predicate | designedToSurpass |
P42712
|
FINISHED |
| Object | Iowa-class battleship |
—
|
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: Iowa-class battleship | Statement: [Montana-class battleship, designedToSurpass, Iowa-class battleship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToSurpass Context triple: [Montana-class battleship, designedToSurpass, Iowa-class battleship]
-
A.
surpasses
chosen
Indicates that one entity exceeds or goes beyond another in degree, quality, performance, or achievement.
-
B.
designedToDefeat
Indicates that one entity is intentionally created or configured with the purpose of overcoming, neutralizing, or rendering ineffective another entity.
-
C.
designedToOutrun
Indicates that one entity was intentionally created or engineered with the capability to move faster than another entity.
-
D.
surpassedStructure
Indicates that one entity has exceeded or gone beyond another entity in terms of structural capacity, performance, or advancement.
-
E.
designedToAvoid
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cd9d474819091b4a80de1019c54 |
completed | April 18, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.