Triple
T25194022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophia Peletier |
E630953
|
entity |
| Predicate | foundAsWalkerAt |
P161446
|
FINISHED |
| Object | Hershel Greene's barn |
—
|
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: Hershel Greene's barn | Statement: [Sophia Peletier, foundAsWalkerAt, Hershel Greene's barn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundAsWalkerAt Context triple: [Sophia Peletier, foundAsWalkerAt, Hershel Greene's barn]
-
A.
foundAs
Indicates that one entity is discovered, identified, or observed in the role, form, or state represented by another entity.
-
B.
foundWith
Indicates that one entity is discovered, observed, or obtained in the presence or company of another entity.
-
C.
foundAfter
Indicates that one entity is discovered or located at a point in time later than another specified entity.
-
D.
foundOver
Indicates that one entity has discovered or identified another entity located above or higher than a reference point or surface.
-
E.
ashFoundIn
Indicates that ash is present within, or has been discovered in, a specified location or material.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 21, 2026, 12:45 p.m.