Triple
T27510399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seaborne Airlines |
E694392
|
entity |
| Predicate | hubTerritory |
P162466
|
FINISHED |
| Object | Puerto Rico |
—
|
NE NERFINISHED |
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: Puerto Rico | Statement: [Seaborne Airlines, hubTerritory, Puerto Rico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hubTerritory Context triple: [Seaborne Airlines, hubTerritory, Puerto Rico]
-
A.
headquartersTerritory
Indicates the territory or region in which an entity’s main headquarters is located.
-
B.
adminTerritory
Indicates that one entity serves as the administrative authority or governing jurisdiction over a specified territory.
-
C.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
D.
refersToTerritory
Indicates that one entity designates, mentions, or is associated with a specific geographic area or territorial domain.
-
E.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef858008190bda723fb47853dce |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:15 p.m.