Triple
T11917449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fredericton International Airport |
E283560
|
entity |
| Predicate | isCertified |
P102335
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fredericton International Airport, isCertified, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCertified Context triple: [Fredericton International Airport, isCertified, yes]
-
A.
hasCertificationLabel
Indicates that an entity bears or is associated with a specific certification label signifying compliance with defined standards or criteria.
-
B.
includesCertification
Indicates that one entity contains, lists, or encompasses a specified certification as part of its attributes or offerings.
-
C.
hasSalesCertification
Indicates that an entity possesses an official certification related to sales skills, knowledge, or qualifications.
-
D.
canCertify
Indicates that one entity has the authority or capability to officially certify another entity or its attributes.
-
E.
hasCertificationStandard
Indicates that an entity complies with, or is associated with, a specific certification standard.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8deb14881909b65a1f159aec65f |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:44 p.m.