Triple
T37331496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stage Manager (Our Town) |
E926762
|
entity |
| Predicate | oftenPlayedBySingleActor |
P196480
|
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: [Stage Manager (Our Town), oftenPlayedBySingleActor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenPlayedBySingleActor Context triple: [Stage Manager (Our Town), oftenPlayedBySingleActor, true]
-
A.
oftenPlayedBy
Indicates that one entity frequently performs, portrays, or executes another entity, such as a role, character, or piece of music.
-
B.
featuresActorInMultipleRoles
Indicates that a work includes an actor who portrays more than one distinct role within that same work.
-
C.
starredActorWith
Indicates that one entity participated as an actor in a production together with another specified actor.
-
D.
arePlayedBy
Indicates that one or more performers (such as actors or musicians) carry out, interpret, or execute the referenced roles, characters, or pieces.
-
E.
associatedWithLeadActorOfFilm
Indicates a relationship where one entity is connected or linked in some relevant way to the lead actor of a specified film.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
| PDg | Predicate description generation | batch_69fe38bc3e9c8190838430b22b82503f |
completed | May 8, 2026, 7:25 p.m. |
Created at: May 3, 2026, 4:16 p.m.