Triple
T2068648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Quadra |
E45964
|
entity |
| Predicate | productLineType |
P11218
|
FINISHED |
| Object | high-end personal computer line |
—
|
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: high-end personal computer line | Statement: [Macintosh Quadra, productLineType, high-end personal computer line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productLineType Context triple: [Macintosh Quadra, productLineType, high-end personal computer line]
-
A.
productLineStart
Indicates the point in time or position at which a particular product line begins or is first introduced.
-
B.
productFamily
chosen
Indicates that one product belongs to, or is categorized under, a broader product family or line.
-
C.
productTypeEvaluated
Indicates that an entity’s product type has been assessed or judged according to certain criteria or standards.
-
D.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
E.
positionInProductLine
Indicates the specific place or order an item occupies within a defined product line or series.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f362f48190b1b0e560424c3aef |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.