Triple
T26835731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polynesian Village Resort |
E675624
|
entity |
| Predicate | hasMonorailService |
P86500
|
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: [Polynesian Village Resort, hasMonorailService, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonorailService Context triple: [Polynesian Village Resort, hasMonorailService, Yes]
-
A.
monorailStation
Indicates that an entity functions as a station or stop specifically for a monorail transit system.
-
B.
monorailLines
chosen
Indicates that there is a monorail transit line or system associated with, serving, or present in the referenced entity.
-
C.
monorailUse
Indicates that one entity makes use of, travels on, or is transported by a monorail system in relation to another entity or context.
-
D.
isOnAutomatedMetroLine
Indicates that something (typically a metro station, segment, or service) belongs to or operates on a metro line that runs with automated (driverless or semi-driverless) train control.
-
E.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 5:04 a.m.