Triple
T28044179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tacoma FD |
E708632
|
entity |
| Predicate | featuresComedyTroupe |
P48234
|
FINISHED |
| Object | Broken Lizard |
—
|
NE NERFINISHED |
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: Broken Lizard | Statement: [Tacoma FD, featuresComedyTroupe, Broken Lizard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresComedyTroupe Context triple: [Tacoma FD, featuresComedyTroupe, Broken Lizard]
-
A.
featuresTroupe
chosen
Indicates that something includes or presents a particular troupe as part of its content or composition.
-
B.
featuresFictionalBand
Indicates that something (such as a work or event) includes or presents a fictional band as part of its content or narrative.
-
C.
featuresVaudeville
Indicates that something includes or presents vaudeville-style performance as a notable element or component.
-
D.
goalOfTroupe
Indicates that a particular objective, purpose, or aim is associated with a specific troupe.
-
E.
mainPerformerLineup
Indicates that the specified entity is part of the primary group of performers featured in a particular event or performance lineup.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 27, 2026, 8:28 p.m.