Triple
T3484851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide Fringe |
E73581
|
entity |
| Predicate | artistParticipation |
P4470
|
FINISHED |
| Object | open to registered artists |
—
|
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: open to registered artists | Statement: [Adelaide Fringe, artistParticipation, open to registered artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artistParticipation Context triple: [Adelaide Fringe, artistParticipation, open to registered artists]
-
A.
performingPartner
Indicates that one entity is the partner who participates in or carries out a performance together with another entity.
-
B.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
C.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
D.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
E.
participation
chosen
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
- 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_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. |
Created at: March 8, 2026, 3:17 p.m.