Triple
T26177009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hitachi HD64180 |
E654568
|
entity |
| Predicate | wasSecondSourcedAs |
P35195
|
FINISHED |
| Object | Zilog Z180 |
—
|
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: Zilog Z180 | Statement: [Hitachi HD64180, wasSecondSourcedAs, Zilog Z180]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSecondSourcedAs Context triple: [Hitachi HD64180, wasSecondSourcedAs, Zilog Z180]
-
A.
hasSecondarySource
chosen
Indicates that an entity is supported, documented, or referenced by a secondary source rather than by a primary or original source.
-
B.
wasSecond
Indicates that one entity held the position or rank of second relative to another in a specified order, sequence, or competition.
-
C.
secondedBy
Indicates that an initial proposal, motion, or action by one entity is formally supported or endorsed by another entity as a second.
-
D.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
E.
requiresSourceDisclosure
Indicates that performing or using something is contingent on revealing or making known the origin or source from which it was derived.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6c9b808190812dcb252b9844f2 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:38 p.m.