Triple
T32350865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Down for It" |
E826590
|
entity |
| Predicate | featuresCountryInstrumentation |
P202872
|
FINISHED |
| Object | true |
—
|
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: true | Statement: ["Down for It", featuresCountryInstrumentation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCountryInstrumentation Context triple: ["Down for It", featuresCountryInstrumentation, true]
-
A.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
B.
languageUsedInInstruments
Indicates that a particular language is employed within the content, interface, or operation of specified instruments or tools.
-
C.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
D.
notableInstrument
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
E.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
- F. None of above. chosen
Provenance (4 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00c9ddd62881909859a36b114a4132 |
completed | May 10, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a00c939b88881909d5353db4265e572 |
completed | May 10, 2026, 6:06 p.m. |
| PDg | Predicate description generation | batch_6a00c9dd1eac8190b33c620ddfae7981 |
completed | May 10, 2026, 6:09 p.m. |
Created at: May 1, 2026, 12:49 a.m.