Triple
T23369928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bing James |
E593436
|
entity |
| Predicate | possibleRoleInEvent |
P4073
|
FINISHED |
| Object | deceased person |
—
|
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: deceased person | Statement: [Bing James, possibleRoleInEvent, deceased person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleRoleInEvent Context triple: [Bing James, possibleRoleInEvent, deceased person]
-
A.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
B.
mayHaveRole
Indicates that an entity is permitted or eligible to hold or perform a specified role.
-
C.
eventRole
chosen
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
D.
relativeInvolvedInEvent
Indicates that a person’s relative participates in, is affected by, or is otherwise involved in a particular event.
-
E.
mayBeInvolvedIn
Indicates that an entity has a possible, but not certain, participation or role in a particular event, activity, or situation.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aff84c8190a5a6bf52adae1c9a |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.