Triple
T36780219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern soul |
E908745
|
entity |
| Predicate | collectorsValue |
P167726
|
FINISHED |
| Object | high for rare singles |
—
|
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 for rare singles | Statement: [Northern soul, collectorsValue, high for rare singles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectorsValue Context triple: [Northern soul, collectorsValue, high for rare singles]
-
A.
collectorValue
chosen
Indicates that something possesses worth or significance specifically as a collectible item, often due to rarity, condition, or desirability among collectors.
-
B.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
C.
collectingField
Indicates that one entity serves as the field or location where another entity gathers, accumulates, or collects items, data, or resources.
-
D.
valuesIn
Indicates that one entity specifies or constrains the set of permissible values for another entity.
-
E.
coreCollectionOf
Indicates that one entity serves as the primary or central collection that another entity belongs to or is grouped within.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:12 p.m.