Triple
T12640433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Performa 580 |
E301879
|
entity |
| Predicate | hasIntegratedSpeakers |
P70173
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Macintosh Performa 580, hasIntegratedSpeakers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntegratedSpeakers Context triple: [Macintosh Performa 580, hasIntegratedSpeakers, yes]
-
A.
hasSpeakerType
Indicates that an entity functions in a particular role or category as a speaker (e.g., narrator, character, announcer) within a given context.
-
B.
hasMicrophones
Indicates that one entity possesses, includes, or is equipped with one or more microphones.
-
C.
numberOfSpeakersStatus
Indicates the status or condition of information about how many speakers are involved (e.g., whether the number of speakers is known, estimated, missing, or otherwise qualified).
-
D.
hasSoundSystem
chosen
Indicates that an entity is equipped with or includes a sound system as one of its features.
-
E.
hasIntegratedUnit
Indicates that one entity includes another entity as a built-in or internally combined component or unit.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:16 p.m.