Triple
T8971080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bournemouth Air Festival |
E214266
|
entity |
| Predicate | hasDisplayArea |
P86005
|
FINISHED |
| Object | over Bournemouth Bay |
—
|
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: over Bournemouth Bay | Statement: [Bournemouth Air Festival, hasDisplayArea, over Bournemouth Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisplayArea Context triple: [Bournemouth Air Festival, hasDisplayArea, over Bournemouth Bay]
-
A.
hasOuterDisplay
Indicates that one entity serves as the external or outward-facing display component of another entity.
-
B.
hasWorkArea
Indicates that one entity possesses, is assigned, or is associated with a specific physical or conceptual work area.
-
C.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
D.
hasAreaRange
Indicates that something’s area falls within a specified minimum-to-maximum range.
-
E.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67672c108190919ae6ca69b6291f |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5fcf24348190b6b845205161c0ee |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:02 p.m.