Triple
T30902911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Mummies Parade |
E787218
|
entity |
| Predicate | transportedItems |
P124266
|
FINISHED |
| Object | royal mummies of ancient Egyptian kings |
—
|
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: royal mummies of ancient Egyptian kings | Statement: [Royal Mummies Parade, transportedItems, royal mummies of ancient Egyptian kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedItems Context triple: [Royal Mummies Parade, transportedItems, royal mummies of ancient Egyptian kings]
-
A.
transportedIn
Indicates that one entity is carried or conveyed inside another entity as a means of transport.
-
B.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
C.
cargoContents
chosen
Indicates that one entity contains or carries another entity as its cargo.
-
D.
commonlyTransportedIn
Indicates that something is usually carried, moved, or conveyed using a particular vehicle, container, or mode of transport.
-
E.
transportedFor
Indicates that one entity was moved or carried from one place to another for the benefit, use, or purpose of another entity or activity.
- 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_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: April 29, 2026, 8:50 p.m.