Triple
T8508106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InformRequest-PDU |
E201384
|
entity |
| Predicate | usedToReport |
P98
|
FINISHED |
| Object | state changes |
—
|
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: state changes | Statement: [InformRequest-PDU, usedToReport, state changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToReport Context triple: [InformRequest-PDU, usedToReport, state changes]
-
A.
canReport
Indicates that one entity has the ability or permission to report on, or submit a report about, another entity or situation.
-
B.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
C.
requiresReportTo
Indicates that one entity is obligated to submit or provide a report to another entity.
-
D.
reportsUsedBy
Indicates that a report is utilized or referenced by another entity (such as a user, system, or process).
-
E.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5df74e8819086b1445cc907e371 |
completed | March 31, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:15 p.m.