Triple
T36844500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Marta |
E910503
|
entity |
| Predicate | hasRegalNickname |
P175311
|
FINISHED |
| Object | "Queen Marta" |
E910503
|
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 Marta" | Statement: [Queen Marta, hasRegalNickname, "Queen Marta"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegalNickname Context triple: [Queen Marta, hasRegalNickname, "Queen Marta"]
-
A.
hasNicknames
Indicates that an entity is known or referred to by one or more alternative informal names.
-
B.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
C.
isOfficialNicknameOf
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
D.
hasRoyalEpithets
chosen
Indicates that an entity is associated with one or more honorific or ceremonial titles traditionally used for royalty.
-
E.
hasRoyalNameElement
Indicates that an entity’s name includes a component that is associated with royalty or a royal title.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dfad8105c8190acdd94fed2db7e89 |
completed | June 26, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.