Triple
T10020196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapMessage |
E200592
|
entity |
| Predicate | extendsInterface |
P91733
|
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: [MapMessage, extendsInterface, Message]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsInterface Context triple: [MapMessage, extendsInterface, Message]
-
A.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
B.
alsoImplements
Indicates that an entity, in addition to its primary implementation, implements another interface, protocol, or specification as well.
-
C.
hasInterface
Indicates that one entity provides, exposes, or is connected through a defined interface to another entity.
-
D.
extendsTo
Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
-
E.
usesImplement
Indicates that one entity employs or makes use of another entity as a tool, instrument, or means to perform an action or achieve a purpose.
- 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.