Triple
T28443810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big Fat Quiz of the Year |
E715781
|
entity |
| Predicate | typicalRecordingLocation |
P8088
|
FINISHED |
| Object | London |
—
|
NE NERFINISHED |
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: London | Statement: [The Big Fat Quiz of the Year, typicalRecordingLocation, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRecordingLocation Context triple: [The Big Fat Quiz of the Year, typicalRecordingLocation, London]
-
A.
placeOfRecording
chosen
Indicates the location where an audio, video, or other recording was made.
-
B.
widelyRecordedIn
Indicates that an event, fact, or phenomenon has been documented or captured in many different records, sources, or media.
-
C.
recordingLocationTour
Indicates the place where a tour-related recording (such as a live performance or tour event) was made.
-
D.
isOftenRecordedOn
Indicates that something is frequently documented, captured, or stored using a particular medium, format, or recording method.
-
E.
reRecordedIn
Indicates that an existing recording of something (e.g., a performance or audio/video content) was made again and captured in a new recording instance.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
Created at: April 28, 2026, 1:47 a.m.