Triple
T11008720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gale Robbins |
E260187
|
entity |
| Predicate | positionInWorks |
P5188
|
FINISHED |
| Object | supporting roles |
—
|
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: supporting roles | Statement: [Gale Robbins, positionInWorks, supporting roles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInWorks Context triple: [Gale Robbins, positionInWorks, supporting roles]
-
A.
positionInWork
chosen
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
B.
positionInPlan
Indicates the specific place or ordering of an element within a larger plan or sequence of planned steps.
-
C.
locationInWork
Indicates that one entity specifies the place or setting where another entity occurs, is situated, or takes place within a particular work (e.g., a scene’s location in a film or a chapter’s setting in a book).
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
coordinatesWorkOf
Indicates overseeing and organizing the tasks, efforts, or activities of others to ensure they work together effectively toward a common goal.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7978810208190b8e2966ae67b6314 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.