Triple
T19206354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Thornton |
E480242
|
entity |
| Predicate | relationshipToBuck |
P95629
|
FINISHED |
| Object | savior |
—
|
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: savior | Statement: [John Thornton, relationshipToBuck, savior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToBuck Context triple: [John Thornton, relationshipToBuck, savior]
-
A.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
B.
relationshipToPete
Indicates the specific type of relationship or connection that an entity has to Pete.
-
C.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
D.
relationshipToJoeBuck
chosen
Indicates the specific familial, social, or professional relationship that one entity has to the person Joe Buck.
-
E.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f99d8ad0819098ebd4ee007149f1 |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:19 p.m.