Triple
T11005646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CC-1 |
E260110
|
entity |
| Predicate | intendedShipType |
P24983
|
FINISHED |
| Object | battlecruiser |
—
|
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: battlecruiser | Statement: [CC-1, intendedShipType, battlecruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedShipType Context triple: [CC-1, intendedShipType, battlecruiser]
-
A.
originalShipType
Indicates the type or category of ship that an entity was originally classified or built as.
-
B.
targetedShip
Indicates that one entity has selected or designated a particular ship as the focus of its attention or action, such as for attack, tracking, or interaction.
-
C.
naveType
Indicates the architectural or structural type or style of a building’s nave in relation to that nave.
-
D.
shipTypeProduced
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
E.
craftType
chosen
Indicates the specific kind or category of craft or vessel associated with an entity.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797562de4819097a0e136180d283a |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.