Triple
T19000411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wollombi Tavern |
E464933
|
entity |
| Predicate | isLocalMeetingPlace |
P13974
|
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: [Wollombi Tavern, isLocalMeetingPlace, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalMeetingPlace Context triple: [Wollombi Tavern, isLocalMeetingPlace, yes]
-
A.
hasMeetingLocation
Indicates that an entity (such as a meeting or event) takes place at or is associated with a specific location.
-
B.
isLocalLandmark
chosen
Indicates that something is recognized as a notable or significant landmark within a specific local area or community.
-
C.
meetsNear
Indicates that two entities meet or come together at a location that is in close proximity to a specified reference point or area.
-
D.
meetsInPlaceOf
Indicates that one entity meets or comes together with another specifically at a designated place or location.
-
E.
meetingPlaceOf
Indicates the location where a particular meeting or gathering takes place or is held for the referenced entities.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6863cf4819096e471d19f9a714c |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.