Triple
T10020182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapMessage |
E200592
|
entity |
| Predicate | messageBodyModel |
P91732
|
FINISHED |
| Object | set of name–value pairs |
—
|
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: set of name–value pairs | Statement: [MapMessage, messageBodyModel, set of name–value pairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageBodyModel Context triple: [MapMessage, messageBodyModel, set of name–value pairs]
-
A.
publicBodyType
Indicates the classification or category of a public body (such as its organizational or legal type) within a governmental or public-sector context.
-
B.
publicBody
Indicates that an entity functions as a governmental or publicly controlled organization that performs public duties or services.
-
C.
body
Indicates that one entity is the physical body or main corporeal form of another entity.
-
D.
bodyConfiguration
Indicates the specific physical arrangement, posture, or structural setup of an entity’s body in relation to its parts or environment.
-
E.
standardBody
Indicates that an entity conforms to a recognized or officially accepted body type, form, or physical specification.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd777b208190ad75eac79eec0c2f |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:53 p.m.