Triple
T35815344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ed Boone |
E1035343
|
entity |
| Predicate | tellsChristopher |
P136407
|
FINISHED |
| Object | his mother is dead |
—
|
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: his mother is dead | Statement: [Ed Boone, tellsChristopher, his mother is dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tellsChristopher Context triple: [Ed Boone, tellsChristopher, his mother is dead]
-
A.
tells
chosen
Indicates that one entity communicates information, a message, or a story to another entity.
-
B.
tellsStoriesIn
Indicates that one entity narrates or recounts stories within or to the context of another entity (such as a place, group, or medium).
-
C.
revealsThat
Indicates that one entity discloses, exposes, or makes known some information, fact, or state of affairs about another entity or situation.
-
D.
triesToRevealTruthTo
Indicates an attempt by one entity to make another entity aware of what it believes to be the true facts or reality of a situation.
-
E.
tellsStoryOver
Indicates that one entity narrates or recounts a story directed toward or in the presence of another entity.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.