Triple
T38059834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Aeronautical Information Publication |
E950308
|
entity |
| Predicate | ADSectionContent |
P34767
|
FINISHED |
| Object | Aerodrome information |
—
|
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: Aerodrome information | Statement: [UK Aeronautical Information Publication, ADSectionContent, Aerodrome information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ADSectionContent Context triple: [UK Aeronautical Information Publication, ADSectionContent, Aerodrome information]
-
A.
article2Content
Indicates that one article serves as the content or body text for another article or higher-level publication entity.
-
B.
articleContent
chosen
Indicates that one entity is the textual or media content that makes up the body of another entity, typically an article or document.
-
C.
centralTextSection
Indicates that one text section functions as the central or primary portion within a larger textual structure or document.
-
D.
adType
Indicates the classification or category of an advertisement associated with an entity or event.
-
E.
sideAContent
Indicates that the content or information pertains specifically to side A of a two-sided entity or relationship.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.