Triple
T29429251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordinary Sinner |
E746379
|
entity |
| Predicate | hasCentralRolePlayedBy |
P171299
|
FINISHED |
| Object | Brendan Hines |
—
|
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: Brendan Hines | Statement: [Ordinary Sinner, hasCentralRolePlayedBy, Brendan Hines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralRolePlayedBy Context triple: [Ordinary Sinner, hasCentralRolePlayedBy, Brendan Hines]
-
A.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
B.
isCentralActorIn
chosen
Indicates that an entity plays the primary or most influential role within a particular event, process, or context.
-
C.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
D.
hasCentralAct
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
-
E.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 3:11 p.m.