Triple
T10531229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isla Holbox |
E248443
|
entity |
| Predicate | commonTransport |
P1379
|
FINISHED |
| Object | golf carts |
—
|
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: golf carts | Statement: [Isla Holbox, commonTransport, golf carts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonTransport Context triple: [Isla Holbox, commonTransport, golf carts]
-
A.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
B.
coordinatesTransportationServicesWith
Indicates that one entity organizes and manages the alignment and collaboration of transportation services with another entity or set of entities.
-
C.
publicTransit
Indicates that one entity provides or is connected via shared, scheduled transportation services (such as buses, trains, or subways) that are available for use by the general public.
-
D.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
E.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a16915c8190ac4f3fd5e43c5fed |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:30 p.m.