Triple
T22027384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3489 |
E544001
|
entity |
| Predicate | specifiesMessageFormat |
P80182
|
FINISHED |
| Object | STUN message header |
—
|
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: STUN message header | Statement: [RFC 3489, specifiesMessageFormat, STUN message header]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesMessageFormat Context triple: [RFC 3489, specifiesMessageFormat, STUN message header]
-
A.
definesMessagePattern
Indicates that one entity specifies or establishes the structural pattern or format that another message or set of messages should follow.
-
B.
hasFormatSpecification
Indicates that something is associated with a particular format definition or specification that describes how it should be structured or represented.
-
C.
definesFormatFor
chosen
Indicates that one entity specifies or establishes the format or structural pattern to be used by another entity.
-
D.
hasLanguageCodeFormat
Indicates that there is a specified structural or syntactic format that language codes associated with an entity must follow.
-
E.
usedFormat
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ccc2ec8190a94d69530d00c06c |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.