Triple
T19000424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wollombi Tavern |
E464933
|
entity |
| Predicate | hasHistoricAtmosphere |
P85831
|
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, hasHistoricAtmosphere, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricAtmosphere Context triple: [Wollombi Tavern, hasHistoricAtmosphere, yes]
-
A.
hasAtmosphericRecord
Indicates that an entity possesses documented data or measurements related to atmospheric conditions or phenomena.
-
B.
hasTraditionalAtmosphere
chosen
Indicates that something possesses a classic, customary, or historically rooted ambiance or mood, often reflecting long-established cultural or social practices.
-
C.
hasEnvironmentalHistory
Indicates that an entity is associated with a record or account of its past environmental conditions, impacts, or interactions.
-
D.
historicalPressure
Indicates a relationship where past events, traditions, or long-standing expectations exert influence or constraint on an entity’s current decisions, behavior, or state.
-
E.
hasHistoricFeatures
Indicates that something possesses characteristics, elements, or attributes of historical significance.
- 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.