Triple
T30649625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Broadway revival |
E780217
|
entity |
| Predicate | PapaGeActor |
P169976
|
FINISHED |
| Object | Merle Dandridge |
—
|
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: Merle Dandridge | Statement: [2017 Broadway revival, PapaGeActor, Merle Dandridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PapaGeActor Context triple: [2017 Broadway revival, PapaGeActor, Merle Dandridge]
-
A.
childActor
Indicates that one entity is an actor who is a child of another entity (typically a parent or guardian).
-
B.
leadActorParent
Indicates that one entity is the parent of the lead actor associated with another entity (such as a film, show, or performance).
-
C.
hasPuppetCharacter
Indicates that one entity features, includes, or is associated with a particular puppet character as part of its content or composition.
-
D.
باب
Indicates a relationship where one entity serves as a door, gate, or entry point to another entity, allowing or controlling access between them.
-
E.
parentAct
Indicates that one entity performs an action in the role of a parent toward another entity, typically involving caregiving, guidance, or parental responsibility.
- 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.