Triple
T37184581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Performa 6100 series |
E921288
|
entity |
| Predicate | sharesCaseDesignWith |
P69276
|
FINISHED |
| Object | Power Macintosh 6100 |
—
|
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: Power Macintosh 6100 | Statement: [Performa 6100 series, sharesCaseDesignWith, Power Macintosh 6100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCaseDesignWith Context triple: [Performa 6100 series, sharesCaseDesignWith, Power Macintosh 6100]
-
A.
sharesCaseWith
Indicates that two entities are involved in, or associated with, the same legal case or proceeding.
-
B.
sharesDesignFeaturesWith
chosen
Indicates that two entities have similar or overlapping design characteristics, structures, or stylistic elements.
-
C.
sharesDesignationTypeWith
Indicates that two entities have the same type or category of designation (e.g., title, label, or classification).
-
D.
sharesMantleWith
Indicates that two entities occupy or are associated with the same mantle, layer, or mantle-like structure.
-
E.
sharesManufacturerWith
Indicates that two entities are produced by the same manufacturer.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00b479c1588190af6e0698b7f8d7f7 |
completed | May 10, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_6a00b4158260819087d0cfad8b18cef4 |
completed | May 10, 2026, 4:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.