Triple
T12569463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Performa 520 |
E295561
|
entity |
| Predicate | hasIntegratedComponent |
P87639
|
FINISHED |
| Object | CRT display |
—
|
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: CRT display | Statement: [Macintosh Performa 520, hasIntegratedComponent, CRT display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntegratedComponent Context triple: [Macintosh Performa 520, hasIntegratedComponent, CRT display]
-
A.
hasIntegratedUnit
chosen
Indicates that one entity includes another entity as a built-in or internally combined component or unit.
-
B.
hasModeIntegration
Indicates that one entity is integrated with, or supports integration of, a particular mode, method, or modality of operation.
-
C.
hasIntegratedCheckPost
Indicates that one entity includes or contains a check post that is functionally integrated within it.
-
D.
hasIntegratedTerminal
Indicates that one entity includes or supports a built-in terminal interface as part of its functionality.
-
E.
integratedIn
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 11:50 p.m.