Triple
T33164091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atago |
E848829
|
entity |
| Predicate | hasClassificationSymbol |
P171641
|
FINISHED |
| Object | CA (heavy cruiser) |
—
|
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: CA (heavy cruiser) | Statement: [Atago, hasClassificationSymbol, CA (heavy cruiser)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClassificationSymbol Context triple: [Atago, hasClassificationSymbol, CA (heavy cruiser)]
-
A.
classificationSymbol
chosen
Indicates that one entity serves as a symbol, label, or marker used to classify or categorize another entity.
-
B.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
C.
hasCharacterClass
Indicates that an entity (such as a character) belongs to or is assigned a particular character class or role type.
-
D.
definesClassification
Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
-
E.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 1, 2026, 1:28 a.m.