Triple
T3484853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide Fringe |
E73581
|
entity |
| Predicate | eventDistribution |
P49043
|
FINISHED |
| Object | events across Adelaide CBD |
—
|
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: events across Adelaide CBD | Statement: [Adelaide Fringe, eventDistribution, events across Adelaide CBD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDistribution Context triple: [Adelaide Fringe, eventDistribution, events across Adelaide CBD]
-
A.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
B.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
C.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
D.
eventDescription
Indicates that a textual summary or explanation is provided describing what happens in the event.
-
E.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
- F. None of above. chosen
Provenance (4 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb795db88190805b26d9774fdb73 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:17 p.m.