Triple
T18917725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John 6 |
E462762
|
entity |
| Predicate | reportsSign |
P133794
|
FINISHED |
| Object | multiplication of loaves and fish |
—
|
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: multiplication of loaves and fish | Statement: [John 6, reportsSign, multiplication of loaves and fish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportsSign Context triple: [John 6, reportsSign, multiplication of loaves and fish]
-
A.
reportsAs
Indicates that one entity formally reports information, status, or results to another entity.
-
B.
reportsFor
Indicates that one entity is subordinate to another and is required to provide updates or answer to that entity, typically within an organizational or hierarchical structure.
-
C.
reportsValueFor
Indicates that one entity provides or communicates the measured or observed value associated with another entity.
-
D.
reportsThrough
Indicates that one entity formally communicates and is accountable to another entity through an established reporting or supervisory chain.
-
E.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c62884988190a362ada1a0a47134 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.