Triple
T18323288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corvo Airport |
E438936
|
entity |
| Predicate | isOnRemoteIsland |
P131381
|
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: [Corvo Airport, isOnRemoteIsland, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnRemoteIsland Context triple: [Corvo Airport, isOnRemoteIsland, true]
-
A.
isInIsland
Indicates that one entity is located within the geographic boundaries of an island.
-
B.
isOnSideOfIsland
Indicates that one entity is located on a particular side or shore of an island relative to some reference or division.
-
C.
hasIslandNearby
Indicates that one location is situated close to an island in geographic space.
-
D.
isRemoteOutpostFor
Indicates that one location functions as a distant, often isolated operational base or support site for another primary location or organization.
-
E.
hasIsland
Indicates that one entity possesses, contains, or includes an island as part of its domain, territory, or structure.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa886508190902ffc26b30731ae |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.