Triple
T27614800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Cypher of Elizabeth II |
E700411
|
entity |
| Predicate | hasMeaningOfLetterR |
P157513
|
FINISHED |
| Object | Regina |
—
|
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: Regina | Statement: [Royal Cypher of Elizabeth II, hasMeaningOfLetterR, Regina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningOfLetterR Context triple: [Royal Cypher of Elizabeth II, hasMeaningOfLetterR, Regina]
-
A.
hasLastThreeLettersMeaning
Indicates that the last three letters of one entity (typically a word or string) together form a meaningful unit or have a specific semantic significance.
-
B.
letterRepresents
chosen
Indicates that a particular letter or character stands for, symbolizes, or denotes a specific value, concept, or entity.
-
C.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
D.
hasLettersFor
Indicates that one entity possesses or contains written correspondence intended for another entity.
-
E.
rootLetters
Indicates that one element specifies the fundamental root letters from which another linguistic form is derived.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 2:12 p.m.