Triple
T31864356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Absolute Dissent |
E813410
|
entity |
| Predicate | featuresOriginalLineup |
P142765
|
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: [Absolute Dissent, featuresOriginalLineup, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresOriginalLineup Context triple: [Absolute Dissent, featuresOriginalLineup, true]
-
A.
lineupFeature
Indicates that an entity is included as a featured item or participant within a specific lineup or roster.
-
B.
notableLineup
Indicates that an entity is recognized as part of a particularly significant or distinguished group, roster, or cast associated with another entity.
-
C.
originalPerformerLineup
chosen
Indicates that the subject is associated with the initial or first group of performers who originally performed an event, work, or production.
-
D.
mainPerformerLineup
Indicates that the specified entity is part of the primary group of performers featured in a particular event or performance lineup.
-
E.
basedOnLineupsOf
Indicates that something is derived from, determined by, or constructed using specific lineups.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a009d623f6c8190b702e2892c52fbb2 |
completed | May 10, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_6a009a3050d48190b64567f28e6ea463 |
completed | May 10, 2026, 2:46 p.m. |
Created at: April 30, 2026, 11:53 p.m.