Triple
T31910901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceiba, Puerto Rico |
E814681
|
entity |
| Predicate | transportGatewayTo |
P37664
|
FINISHED |
| Object | Vieques |
—
|
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: Vieques | Statement: [Ceiba, Puerto Rico, transportGatewayTo, Vieques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportGatewayTo Context triple: [Ceiba, Puerto Rico, transportGatewayTo, Vieques]
-
A.
transportInterface
Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
-
B.
transportConnectionTo
chosen
Indicates a relationship where one entity provides or participates in a means of transportation that connects or leads to another entity.
-
C.
transportFrom
Indicates that something or someone is moved or carried away starting from a specified origin location.
-
D.
transportFor
Indicates a relationship where one entity serves as the means or service used to move another entity from one place to another.
-
E.
transportAgnostic
Indicates that the relationship or action is independent of, and unaffected by, the specific transport mechanism or communication channel used.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 1, 2026, 12:01 a.m.