Triple
T3856524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmonton Fringe Theatre Festival |
E90028
|
entity |
| Predicate | selectionPolicy |
P136
|
FINISHED |
| Object | non-juried |
—
|
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: non-juried | Statement: [Edmonton Fringe Theatre Festival, selectionPolicy, non-juried]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionPolicy Context triple: [Edmonton Fringe Theatre Festival, selectionPolicy, non-juried]
-
A.
decisionPublicationPolicy
Indicates the policy or rules governing how decisions are made public or communicated.
-
B.
ordinationPolicy
Indicates the rules or criteria governing how entities are ordered, ranked, or arranged relative to one another.
-
C.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
D.
selectionProcess
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
E.
simplificationPolicy
Indicates a relationship where one entity defines or applies rules for simplifying, reducing, or streamlining another entity, process, or representation.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec07d45081909b8f3e35eb710f4c |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.