Triple
T5818593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CST (Cuba) |
E129047
|
entity |
| Predicate | appliesToMainland |
P67139
|
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: [CST (Cuba), appliesToMainland, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToMainland Context triple: [CST (Cuba), appliesToMainland, yes]
-
A.
connectedToMainlandBy
Indicates that one landmass or area is physically linked to a mainland, typically via a bridge, causeway, or other continuous connection.
-
B.
appliesToSovereignState
Indicates that something (such as a rule, status, or attribute) is applicable to, or in effect for, a sovereign state.
-
C.
appliesToAdministrativeTerritory
Indicates that something (such as a rule, measure, or status) is valid for, relevant to, or in force within a specific administrative territory.
-
D.
appliesToTerritorialWatersOf
Indicates that something (such as a rule, status, or condition) is applicable within the territorial waters of a specified entity.
-
E.
hasAdjacentMainlandArea
Indicates that one geographic area directly borders or touches a contiguous mainland region.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c0400dbec08190b2ef73689b2c0c31 |
completed | March 22, 2026, 7:16 p.m. |
Created at: March 22, 2026, 3:53 p.m.