Triple
T6775648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobart-class destroyer |
E155146
|
entity |
| Predicate | namedShipType |
P3141
|
FINISHED |
| Object | Australian cities |
—
|
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: Australian cities | Statement: [Hobart-class destroyer, namedShipType, Australian cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedShipType Context triple: [Hobart-class destroyer, namedShipType, Australian cities]
-
A.
shipClass
chosen
Indicates the classification or type category to which a particular ship belongs.
-
B.
shipTypeProduced
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
C.
originalShipType
Indicates the type or category of ship that an entity was originally classified or built as.
-
D.
shipName
Indicates the name assigned to a specific ship in the relationship.
-
E.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24f77c88190be21cf4ef132aa31 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.