Triple
T33435591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Information API |
E856231
|
entity |
| Predicate | providesEvent |
P93441
|
FINISHED |
| Object | change |
—
|
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: change | Statement: [Network Information API, providesEvent, change]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesEvent Context triple: [Network Information API, providesEvent, change]
-
A.
servesEvent
Indicates that an entity provides, hosts, or facilitates a particular event for others.
-
B.
exposesEvent
chosen
Indicates that one entity makes an event available or visible for use, handling, or observation by another entity or system.
-
C.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
D.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
E.
servesEventType
Indicates that an entity provides or supports a particular type or category of event.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 1, 2026, 1:36 a.m.