Triple
T30902906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Mummies Parade |
E787218
|
entity |
| Predicate | showcasedTo |
P130339
|
FINISHED |
| Object | global audience |
—
|
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: global audience | Statement: [Royal Mummies Parade, showcasedTo, global audience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showcasedTo Context triple: [Royal Mummies Parade, showcasedTo, global audience]
-
A.
helpedShowcase
Indicates that one entity actively assisted in presenting, promoting, or displaying another entity to an audience.
-
B.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
C.
presentedIn
Indicates that something is shown, displayed, or formally introduced within a particular context, medium, event, or setting.
-
D.
exhibitedAs
Indicates that something is presented or displayed in a particular context, such as in a show, gallery, or exhibition.
-
E.
exhibitFor
chosen
Indicates a relationship where something is displayed, presented, or shown for the benefit, use, or consideration of a particular audience, purpose, or 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:50 p.m.