Triple
T27936461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trail Mix-Up |
E700625
|
entity |
| Predicate | featuresSlapstick |
P195489
|
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: [Trail Mix-Up, featuresSlapstick, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSlapstick Context triple: [Trail Mix-Up, featuresSlapstick, true]
-
A.
specialFeatures
Indicates the distinctive or additional characteristics, functionalities, or attributes that set an entity apart from standard or typical versions.
-
B.
featuresVaudeville
Indicates that something includes or presents vaudeville-style performance as a notable element or component.
-
C.
featuresFranchise
Indicates that one entity includes or presents a particular franchise as part of its content, offering, or composition.
-
D.
featuresFictionalProgram
Indicates that a work includes or presents a fictional program (such as a TV show, software, or in-universe broadcast) as part of its content.
-
E.
featuresGame
Indicates that something (such as a platform, service, or collection) includes or presents a particular game as part of its offerings.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69fdd5faea908190a17d77e050362ef5 |
completed | May 8, 2026, 12:24 p.m. |
Created at: April 27, 2026, 7:13 p.m.