Triple
T3285386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tequila Gang |
E68967
|
entity |
| Predicate | hasWorkStyle |
P47713
|
FINISHED |
| Object | dark visual tone |
—
|
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: dark visual tone | Statement: [Tequila Gang, hasWorkStyle, dark visual tone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkStyle Context triple: [Tequila Gang, hasWorkStyle, dark visual tone]
-
A.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
B.
hasWorkPeriod
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
-
C.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
D.
workMode
Indicates the manner, configuration, or operational state in which an entity performs its work or function.
-
E.
hasWorkAsSubject
Indicates that an entity serves as the subject (creator or originator) of a particular work or creative output.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb03918c48190987d7cfd3bda9716 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.