Triple
T11757814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Dalmatian |
E279569
|
entity |
| Predicate | hasCollectibleStatus |
P2370
|
FINISHED |
| Object | sought-after iMac G3 variant among collectors |
—
|
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: sought-after iMac G3 variant among collectors | Statement: [Blue Dalmatian, hasCollectibleStatus, sought-after iMac G3 variant among collectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectibleStatus Context triple: [Blue Dalmatian, hasCollectibleStatus, sought-after iMac G3 variant among collectors]
-
A.
collectingStatus
Indicates the current state or phase of an ongoing collection process or activity.
-
B.
collectibleIn
Indicates that one entity can be collected or obtained within the context, location, or container defined by another entity.
-
C.
hasRelicsStatus
Indicates that an entity holds a particular status or condition specifically related to relics.
-
D.
canCollect
Indicates that one entity has the ability or permission to gather, receive, or take possession of another entity.
-
E.
collectibleAspect
chosen
Indicates that one entity represents a collectible-related characteristic, feature, or dimension associated with 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5220f148190ae60d1941a579ab6 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.