Triple
T4164577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaumont Park (Cork) |
E84413
|
entity |
| Predicate | typicalVisitorType |
P1284
|
FINISHED |
| Object | local residents |
—
|
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: local residents | Statement: [Beaumont Park (Cork), typicalVisitorType, local residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVisitorType Context triple: [Beaumont Park (Cork), typicalVisitorType, local residents]
-
A.
hasVisitorType
chosen
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
B.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
C.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
-
D.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
E.
primaryVisitors
Indicates that certain entities are the main or most important visitors associated with another entity or context.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.