Triple
T2899704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corniche, Abu Dhabi |
E62624
|
entity |
| Predicate | bestVisitedIn |
P31097
|
FINISHED |
| Object | cooler months (roughly November to March) |
—
|
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: cooler months (roughly November to March) | Statement: [Corniche, Abu Dhabi, bestVisitedIn, cooler months (roughly November to March)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestVisitedIn Context triple: [Corniche, Abu Dhabi, bestVisitedIn, cooler months (roughly November to March)]
-
A.
bestVisitedAt
chosen
Indicates the optimal time or conditions under which a place or entity should be visited.
-
B.
wasFirstVisitedBy
Indicates that a particular entity was initially reached, discovered, or visited by another specified entity before any others.
-
C.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
D.
visitedFor
Indicates that one entity traveled to or attended another entity (such as a place, person, or event) for a specific purpose or reason.
-
E.
frequentlyVisitedBy
Indicates that an entity is regularly or often visited by another 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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abe0ad7bbc8190822738baa6935b74 |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:10 p.m.