Triple
T33434031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MessageEvent |
E856200
|
entity |
| Predicate | eventTypeExample |
P31609
|
FINISHED |
| Object | "message" |
—
|
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: "message" | Statement: [MessageEvent, eventTypeExample, "message"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventTypeExample Context triple: [MessageEvent, eventTypeExample, "message"]
-
A.
eventUsage
Indicates how an event is employed, applied, or utilized within a particular context or process.
-
B.
eventLevel
Indicates the intensity, magnitude, or severity associated with an event within a defined scale or hierarchy.
-
C.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
D.
eventName
chosen
Indicates the specific label or title assigned to identify an event within a system or context.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger 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_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:36 a.m.