Triple
T9971338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whale Cay |
E196210
|
entity |
| Predicate | termCayMeans |
P24083
|
FINISHED |
| Object | small low-elevation island |
—
|
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: small low-elevation island | Statement: [Whale Cay, termCayMeans, small low-elevation island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termCayMeans Context triple: [Whale Cay, termCayMeans, small low-elevation island]
-
A.
includesCay
Indicates that something contains or encompasses a cay (a small, low-elevation, sandy island on a coral reef) within its area or composition.
-
B.
typicalTerm
Indicates that something is a standard, representative, or characteristic term typically associated with a given concept or context.
-
C.
keyTerm
Indicates that a term functions as a primary or central concept within a given context or information structure.
-
D.
termType
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
E.
languageTerm
chosen
Indicates that one entity is a linguistic expression (word, phrase, or term) used to denote or label the other entity.
- F. None of above.
Provenance (3 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b96b1c8190b9d3c1171346615a |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.