Triple
T1177570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will Parker |
E25062
|
entity |
| Predicate | hasStagePortrayal |
P1507
|
FINISHED |
| Object | various Broadway actors |
—
|
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: various Broadway actors | Statement: [Will Parker, hasStagePortrayal, various Broadway actors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStagePortrayal Context triple: [Will Parker, hasStagePortrayal, various Broadway actors]
-
A.
portrayedByWork
Indicates that a work (such as a film, book, or artwork) depicts, represents, or portrays a particular entity.
-
B.
portraysActorAs
Indicates that one entity depicts or represents an actor in a particular role, character, or manner.
-
C.
isMainStageOf
Indicates that one entity serves as the primary or central stage or platform on which the other entity occurs, is presented, or is featured.
-
D.
portrayedBy
chosen
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
-
E.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.