Triple
T34706288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porto da Barra Beach |
E1000513
|
entity |
| Predicate | hasEventUsage |
P42697
|
FINISHED |
| Object | New Year celebrations |
—
|
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: New Year celebrations | Statement: [Porto da Barra Beach, hasEventUsage, New Year celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventUsage Context triple: [Porto da Barra Beach, hasEventUsage, New Year celebrations]
-
A.
hasEventFrequency
Indicates how often a particular event occurs within a given time period.
-
B.
eventUsage
chosen
Indicates how an event is employed, applied, or utilized within a particular context or process.
-
C.
hasEventTrafficFor
Indicates that there is traffic information or conditions specifically associated with a particular event.
-
D.
hasEventSpace
Indicates that an entity provides or includes a designated space intended for hosting events.
-
E.
hasDedicatedEvent
Indicates that a specific event is explicitly organized or reserved for the referenced entity or relationship.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.