Triple
T3743822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh Festival Fringe |
E79762
|
entity |
| Predicate | hasRegistrationSystem |
P29001
|
FINISHED |
| Object | open to any performer with a venue and fee |
—
|
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 any performer with a venue and fee | Statement: [Edinburgh Festival Fringe, hasRegistrationSystem, open to any performer with a venue and fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegistrationSystem Context triple: [Edinburgh Festival Fringe, hasRegistrationSystem, open to any performer with a venue and fee]
-
A.
registrationSystem
Indicates a system or process responsible for recording, managing, and maintaining registrations or enrollments for entities.
-
B.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
C.
supportsRegistration
chosen
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
D.
registrationMode
Indicates the method or process by which something is registered or enrolled.
-
E.
hasPASystem
Indicates that an entity possesses or is equipped with a public address (PA) system.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb576b5881908515d64c71f11a16 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.