Triple
T33120765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eton College Choir |
E847588
|
entity |
| Predicate | performsBeyond |
P270
|
FINISHED |
| Object | concert venues outside Eton College |
—
|
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: concert venues outside Eton College | Statement: [Eton College Choir, performsBeyond, concert venues outside Eton College]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsBeyond Context triple: [Eton College Choir, performsBeyond, concert venues outside Eton College]
-
A.
performsWellOn
Indicates that one entity achieves good results or high performance when evaluated using, or operating within, another entity (such as a task, test, or environment).
-
B.
performsAs
Indicates that one entity takes on, enacts, or fulfills the role, function, or character of another entity.
-
C.
performsFrom
Indicates that an action, performance, or operation is carried out starting from a particular source, origin, or initial context.
-
D.
performsAt
chosen
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
-
E.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 1, 2026, 1:27 a.m.