Triple
T15386453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaiju War |
E367927
|
entity |
| Predicate | enemyClassificationSystem |
P110665
|
FINISHED |
| Object | kaiju category scale |
—
|
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: kaiju category scale | Statement: [Kaiju War, enemyClassificationSystem, kaiju category scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyClassificationSystem Context triple: [Kaiju War, enemyClassificationSystem, kaiju category scale]
-
A.
classificationSystem
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
B.
classificationSystemBasedOn
chosen
Indicates that one classification system is organized, defined, or derived using another classification system as its basis or reference framework.
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
classifiesForceAs
Indicates that one entity assigns or identifies a specific type or category to a given force.
-
E.
enemyType
Indicates that one entity is classified as an enemy of a specified type or category in relation to 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e74ff70819094c1a85f51d6e228 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.