Triple
T17998808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IAYP |
E430569
|
entity |
| Predicate | isDeliveredThrough |
P130074
|
FINISHED |
| Object | schools |
—
|
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: schools | Statement: [IAYP, isDeliveredThrough, schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDeliveredThrough Context triple: [IAYP, isDeliveredThrough, schools]
-
A.
deliveredFrom
Indicates that something has been sent, transported, or provided from a particular source or origin to another party or location.
-
B.
designedToBeDeliveredBy
Indicates that one entity is intentionally created or configured so that it will be transported, distributed, or handed over by another specified entity.
-
C.
deliveredBy
Indicates that something (such as a product, message, or service) is brought, transported, or provided to its destination by a specified agent or carrier.
-
D.
offersDeliveryTo
Indicates that one entity provides delivery services to another entity or location.
-
E.
offersDelivery
Indicates that a provider makes goods or services available to be transported and delivered to a recipient’s specified location.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e6a2a881908af2d0a4a5053916 |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:23 a.m.