Triple
T29453695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeronautical Fixed Telecommunication Network |
E747042
|
entity |
| Predicate | messageFormatIncludes |
P33419
|
FINISHED |
| Object | heading |
—
|
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: heading | Statement: [Aeronautical Fixed Telecommunication Network, messageFormatIncludes, heading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageFormatIncludes Context triple: [Aeronautical Fixed Telecommunication Network, messageFormatIncludes, heading]
-
A.
includeFormat
chosen
Indicates that one entity contains or specifies the format or representation type of another entity.
-
B.
hasMatchFormat
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
-
C.
meetsFormat
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
-
D.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
E.
componentIncluded
Indicates that one entity is a constituent part or subcomponent that is contained within or included in 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b6b17c48190899f49d33946738e |
completed | May 2, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:34 p.m.