Triple
T3484820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide Fringe |
E73581
|
entity |
| Predicate | openAccess |
P1079
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Adelaide Fringe, openAccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openAccess Context triple: [Adelaide Fringe, openAccess, true]
-
A.
openAccessPolicy
Indicates that an entity has a policy allowing unrestricted or minimally restricted public access to its resources, content, or services.
-
B.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
C.
publicAccess
chosen
Indicates that something is available for use, entry, or viewing by the general public without special restrictions or permissions.
-
D.
openAccessDelay
Indicates the length of time between an item’s initial restricted publication and when it becomes freely accessible to the public.
-
E.
openedForPublic
Indicates that something has been made accessible or available for use, entry, or participation by the general public.
- 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.