Triple
T34024347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caledonian societies in Australia |
E872464
|
entity |
| Predicate | typicalEventFeature |
P5084
|
FINISHED |
| Object | tartan displays |
—
|
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: tartan displays | Statement: [Caledonian societies in Australia, typicalEventFeature, tartan displays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEventFeature Context triple: [Caledonian societies in Australia, typicalEventFeature, tartan displays]
-
A.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
B.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
C.
typicalFeatures
chosen
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
D.
typicalEventDay
Indicates the day on which an event is normally or most commonly held or occurs.
-
E.
featuresEventsFor
Indicates that something presents, highlights, or includes specific events as part of its content or offering.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:51 a.m.