Triple
T24220401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Todd |
E601435
|
entity |
| Predicate | forcesToRead |
P155241
|
FINISHED |
| Object | Tony Last |
—
|
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: Tony Last | Statement: [Mr. Todd, forcesToRead, Tony Last]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcesToRead Context triple: [Mr. Todd, forcesToRead, Tony Last]
-
A.
readsTo
Indicates that one entity reads or recites content aloud for the benefit of another entity.
-
B.
readsFrom
Indicates that one entity obtains or accesses data, information, or content from another entity as a source.
-
C.
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).
-
D.
typeOfForcesDirected
Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
-
E.
inForceIn
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820cdd3c8190998d6d901224c09f |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 17, 2026, 11:59 p.m.