Triple
T29246990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zorro II |
E741465
|
entity |
| Predicate | electricalBasis |
P145380
|
FINISHED |
| Object | Motorola 68000 bus |
—
|
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: Motorola 68000 bus | Statement: [Zorro II, electricalBasis, Motorola 68000 bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricalBasis Context triple: [Zorro II, electricalBasis, Motorola 68000 bus]
-
A.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
B.
electricalSystem
Indicates that one entity functions as, is part of, or is directly related to the electrical system of another entity.
-
C.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
D.
engineeringBasis
chosen
Indicates that something serves as the foundational technical or engineering rationale, justification, or underlying basis for another entity or decision.
-
E.
isElectrically
Indicates that one entity has an electrical property, connection, or interaction 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 28, 2026, 12:33 p.m.