Triple
T36833218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Elizabeth II in The Announcement |
E910201
|
entity |
| Predicate | hasTitleInNarrative |
P3254
|
FINISHED |
| Object | Queen Elizabeth II |
E786
|
NE 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: Queen Elizabeth II | Statement: [Queen Elizabeth II in The Announcement, hasTitleInNarrative, Queen Elizabeth II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleInNarrative Context triple: [Queen Elizabeth II in The Announcement, hasTitleInNarrative, Queen Elizabeth II]
-
A.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
B.
hasTitleNote
Indicates that an entity has an associated note or annotation specifically about its title.
-
C.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
D.
isTitled
Indicates that an entity holds or is assigned a specific formal title or designation.
-
E.
containsTitle
chosen
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
- F. None of above.
Provenance (4 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dfac555388190a2d7df37c0c2db2c |
completed | June 26, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:13 p.m.