Triple
T597701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson 'Jax' Teller |
E11422
|
entity |
| Predicate | reads |
P9917
|
FINISHED |
| Object | John Teller's manuscript |
—
|
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: John Teller's manuscript | Statement: [Jackson 'Jax' Teller, reads, John Teller's manuscript]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reads Context triple: [Jackson 'Jax' Teller, reads, John Teller's manuscript]
-
A.
readership
chosen
Indicates the relationship in which one party reads, follows, or is the audience for the written or published work of another.
-
B.
requiredReadingFor
Indicates that one item (such as a text or resource) must be read as a mandatory prerequisite or component for engaging with, understanding, or completing another item (such as a course, assignment, or program).
-
C.
rite
Indicates a ceremonial or ritual action performed according to established traditions or religious practices.
-
D.
readingsCycle
Indicates that there is a recurring or cyclical pattern in the readings associated with an entity or process.
-
E.
wrote
Indicates that an entity is the author or creator of a written work involving 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49dc4f7d08190990f70b9b3af6ce5 |
completed | March 1, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69a49cf59cd0819084e67981cb371e25 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.