Triple
T8679890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark-5 |
E206009
|
entity |
| Predicate | hasOperationalEra |
P77920
|
FINISHED |
| Object | late stages of the kaiju war |
—
|
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: late stages of the kaiju war | Statement: [Mark-5, hasOperationalEra, late stages of the kaiju war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperationalEra Context triple: [Mark-5, hasOperationalEra, late stages of the kaiju war]
-
A.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
B.
hasPrimaryEra
chosen
Indicates that an entity is chiefly associated with or belongs to a particular historical or temporal era.
-
C.
hasEraReset
Indicates that a new era or time period has been initiated, resetting the previous temporal sequence or counting.
-
D.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
E.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.