Triple
T33505149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinite Guitar |
E858091
|
entity |
| Predicate | enablesTechnique |
P3047
|
FINISHED |
| Object | long drones |
—
|
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: long drones | Statement: [Infinite Guitar, enablesTechnique, long drones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesTechnique Context triple: [Infinite Guitar, enablesTechnique, long drones]
-
A.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
-
B.
enablesTechnology
Indicates that one entity makes it possible for another entity, system, or process to function through the use or provision of a particular technology.
-
C.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
D.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
-
E.
techniqueRequired
Indicates that performing one entity (such as an action, process, or task) necessitates the use of a specific technique associated with the other 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e59ed5388190b4db22e945b40e20 |
completed | May 3, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69f6e3db74c081909a991309d835d477 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.