Triple
T28772337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z 5600 |
E726444
|
entity |
| Predicate | hasSuccessorClass |
P10131
|
FINISHED |
| Object | Z 8800 |
—
|
NE NERFINISHED |
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: Z 8800 | Statement: [Z 5600, hasSuccessorClass, Z 8800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorClass Context triple: [Z 5600, hasSuccessorClass, Z 8800]
-
A.
successorClass
chosen
Indicates that one class directly follows or replaces another class in a sequence or hierarchy.
-
B.
hasNotableSuccessorType
Indicates that an entity has a successor whose type or category is considered notably significant or distinguished in relation to it.
-
C.
hasCurrentSuccessor
Indicates that one entity is the immediate next or following entity in a current, ordered sequence or progression of another entity.
-
D.
hasMoreAggressiveSuccessor
Indicates that one entity is followed or replaced by another entity that exhibits a higher level of aggressiveness in behavior, strategy, or effect.
-
E.
hasFlagshipSuccessor
Indicates that one entity serves as the primary or leading successor to another, typically replacing it as the main or flagship version, product, or instance.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 28, 2026, 6:16 a.m.