Triple
T35419732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Skiles |
E1023747
|
entity |
| Predicate | notableEventDestination |
P206975
|
FINISHED |
| Object | Charlotte Douglas International Airport |
E24755
|
NE 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: Charlotte Douglas International Airport | Statement: [Jeffrey Skiles, notableEventDestination, Charlotte Douglas International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventDestination Context triple: [Jeffrey Skiles, notableEventDestination, Charlotte Douglas International Airport]
-
A.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
B.
notableAIEvent
Indicates that an event is recognized as significant or influential within the field of artificial intelligence.
-
C.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
D.
notableEventServed
Indicates that an entity served in an official or significant capacity during a notable event.
-
E.
bearerNotableEvent
Indicates that a bearer (such as a person or entity) is associated with a specific notable event in which they played a significant role.
- F. None of above. chosen
Provenance (5 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3836b3b03c819094bcb32130a37495 |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.