Triple
T349820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jose International Airport |
E7416
|
entity |
| Predicate | hasInternationalService |
P11099
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [San Jose International Airport, hasInternationalService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternationalService Context triple: [San Jose International Airport, hasInternationalService, true]
-
A.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
B.
hasInternationalVersion
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
-
C.
couldServeOverseas
Indicates that an entity has the ability or eligibility to perform service or duties in a foreign or overseas location.
-
D.
isMajorInternationalGatewayFor
Indicates that one entity serves as a primary, globally significant access point or hub for another entity’s international connections or flows.
-
E.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb1f028c819098fa6480b4ca5cf0 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.