Triple
T8425404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disco Club |
E198971
|
entity |
| Predicate | hasPrimaryIntendedUse |
P88
|
FINISHED |
| Object | dancefloor performance |
—
|
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: dancefloor performance | Statement: [Disco Club, hasPrimaryIntendedUse, dancefloor performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryIntendedUse Context triple: [Disco Club, hasPrimaryIntendedUse, dancefloor performance]
-
A.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
B.
isBelievedToBeUsedFor
Indicates that something is thought or assumed to serve a particular purpose or function, without certainty.
-
C.
originalPrimaryUse
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
D.
hasPrimaryFunction
chosen
Indicates that one entity serves as the main or principal function or role of another entity.
-
E.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb85a2871081908a4093838fc93b5a |
completed | March 31, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69cb70d7ea348190aafbf8ca02b7b7d5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:07 p.m.