Triple
T7083441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugh Herbert Hipple |
E165012
|
entity |
| Predicate | stage actor |
P44516
|
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: [Hugh Herbert Hipple, stage actor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stage actor Context triple: [Hugh Herbert Hipple, stage actor, true]
-
A.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
B.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
-
C.
theaterRole
chosen
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
-
D.
employedActor
Indicates that one entity has hired or currently employs another entity to perform work or services.
-
E.
stagePortrayalIncludes
Indicates that a stage portrayal incorporates or features a particular element, character, action, or aspect within the performance.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5102be08190bbde790bfa8fe9e2 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.