Triple
T13518563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Elizabethan Theatre Trust |
E322831
|
entity |
| Predicate | sponsoredActivity |
P24549
|
FINISHED |
| Object | theatre productions |
—
|
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: theatre productions | Statement: [Australian Elizabethan Theatre Trust, sponsoredActivity, theatre productions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsoredActivity Context triple: [Australian Elizabethan Theatre Trust, sponsoredActivity, theatre productions]
-
A.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
B.
sponsoredPrograms
chosen
Indicates that an entity provides financial or resource support to specific programs or initiatives.
-
C.
sportsSponsored
Indicates that one entity provides financial or material sponsorship to support another entity’s sports-related activities or events.
-
D.
sponsorFrom
Indicates that one entity provides sponsorship or financial backing originating from a specified source entity.
-
E.
associatedActivity
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa27f048190bed33a98e28c8d09 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:44 p.m.