Triple
T30649624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Broadway revival |
E780217
|
entity |
| Predicate | TiMouneActor |
P169975
|
FINISHED |
| Object | Hailey Kilgore |
—
|
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: Hailey Kilgore | Statement: [2017 Broadway revival, TiMouneActor, Hailey Kilgore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TiMouneActor Context triple: [2017 Broadway revival, TiMouneActor, Hailey Kilgore]
-
A.
MiramboRole
Indicates that an entity holds a specific role, position, or function in relation to Mirambo.
-
B.
tempoCharacter
Indicates the characteristic speed or pacing quality associated with an action, event, or process.
-
C.
motionCapturePerformer
Indicates a relationship where a performer provides motion data, typically through sensors or tracking, to drive the movement of a digital character or animation.
-
D.
robotCharacter
Indicates that an entity is characterized as a robot, typically possessing mechanical or artificial attributes that define its nature or role.
-
E.
Tor-M2K
Indicates a defensive relationship where the Tor-M2K system detects, tracks, and engages aerial or missile threats to protect designated assets or areas.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a9639048190b515dfe149c59aba |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:30 p.m.