Triple
T193781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Utah (AG-16) |
E3774
|
entity |
| Predicate | shipTypeBeforeConversion |
P3141
|
FINISHED |
| Object | 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: battleship | Statement: [USS Utah (AG-16), shipTypeBeforeConversion, battleship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipTypeBeforeConversion Context triple: [USS Utah (AG-16), shipTypeBeforeConversion, battleship]
-
A.
shipClass
chosen
Indicates the classification or type category to which a particular ship belongs.
-
B.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
C.
sisterShip
Indicates that two ships are considered counterparts or equivalents, typically of the same design, class, or series.
-
D.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
E.
rollingStockType
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a2596810c48190ab687c0c2efaa9e2 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a256769ad8819083c1d83082c0215e |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.