Triple
T27510973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citizen Smith |
E694410
|
entity |
| Predicate | Wolfie SmithPortrayedBy |
P162467
|
FINISHED |
| Object | Robert Lindsay |
—
|
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: Robert Lindsay | Statement: [Citizen Smith, Wolfie SmithPortrayedBy, Robert Lindsay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Wolfie SmithPortrayedBy Context triple: [Citizen Smith, Wolfie SmithPortrayedBy, Robert Lindsay]
-
A.
roleRupertGrint
Indicates that the entity has the role or character portrayed by Rupert Grint in a work or context.
-
B.
Jack Hively
Indicates a relationship or action involving the person named Jack Hively, such as authorship, direction, or participation in a work or event.
-
C.
الحفيد
Indicates a grandchild relationship, where one entity is the descendant (grandson or granddaughter) of another entity’s child.
-
D.
Libby
Indicates a relationship or action involving Libby, though the specific nature of the relationship is not defined by the predicate name alone.
-
E.
belovedCharacter
Indicates that one entity is a character who is deeply loved, cherished, or held in special affection by another entity.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef94b488190825d38e24496b755 |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:16 p.m.