Triple
T36982538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plattsburgh International Airport |
E914869
|
entity |
| Predicate | cityMarketingSlogan |
P77422
|
FINISHED |
| Object | Montreal’s U.S. airport |
—
|
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: Montreal’s U.S. airport | Statement: [Plattsburgh International Airport, cityMarketingSlogan, Montreal’s U.S. airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityMarketingSlogan Context triple: [Plattsburgh International Airport, cityMarketingSlogan, Montreal’s U.S. airport]
-
A.
tourismSlogan
Indicates that a phrase is used as a promotional slogan to attract tourists to a place or destination.
-
B.
sloganConcept
Indicates that a particular concept, idea, or theme is expressed or represented by a given slogan.
-
C.
sloganInspired
Indicates that one slogan was created, influenced, or shaped by ideas, style, or content drawn from another source.
-
D.
centralSloganFor
chosen
Indicates that one expression or phrase serves as the main or defining slogan for a particular entity, campaign, or initiative.
-
E.
sloganCategory
Indicates that a slogan is classified as belonging to a particular category or type.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.