Triple
T24963884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haad Yuan |
E624683
|
entity |
| Predicate | hasNearbyEventHub |
P162980
|
FINISHED |
| Object | Full Moon Party at Haad Rin |
—
|
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: Full Moon Party at Haad Rin | Statement: [Haad Yuan, hasNearbyEventHub, Full Moon Party at Haad Rin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyEventHub Context triple: [Haad Yuan, hasNearbyEventHub, Full Moon Party at Haad Rin]
-
A.
hasNearbyEvent
Indicates that an event occurs close in space or time to the referenced entity.
-
B.
hasNearbyEventType
Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
-
C.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
D.
hasNearbyPoint
Indicates that one entity has at least one other point located within a specified proximity or distance from it.
-
E.
hasNearbyGate
Indicates that one entity has a gate located in close physical proximity to it.
- F. None of above. chosen
Provenance (4 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 18, 2026, 5:59 a.m.