Triple
T14797877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Glele |
E347825
|
entity |
| Predicate | usedRoyalSymbol |
P29556
|
FINISHED |
| Object | lion |
—
|
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: lion | Statement: [King Glele, usedRoyalSymbol, lion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRoyalSymbol Context triple: [King Glele, usedRoyalSymbol, lion]
-
A.
usesImperialRegalia
Indicates that one entity employs or incorporates imperial regalia (such as crowns, scepters, or other sovereign insignia) in relation to another entity or context.
-
B.
ceremonialSymbol
Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
-
C.
hasRoyalCircle
Indicates that an entity belongs to, is part of, or is associated with a royal or monarch’s inner circle or court.
-
D.
royalVariant
Indicates a relationship where one entity is a special or modified version of another that is associated with royalty, nobility, or regal status.
-
E.
emblemUsedBy
chosen
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd6131f08190885f1d27b4bfac7a |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.