Triple
T25562079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubd'sco Vol. 1 |
E640739
|
entity |
| Predicate | isInstrumentalDominant |
P19640
|
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: [Dubd'sco Vol. 1, isInstrumentalDominant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInstrumentalDominant Context triple: [Dubd'sco Vol. 1, isInstrumentalDominant, true]
-
A.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
B.
isInstrumental
Indicates that one entity serves as the means, tool, or instrument by which another entity performs an action or achieves an outcome.
-
C.
instrumentalIn
chosen
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
-
D.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
E.
definesAsInstrumental
Indicates that one entity is characterized or designated as serving an instrumental or means-to-an-end role in relation to another entity or context.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8f9bc48819097a98b805f60d5dd |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:46 p.m.