Triple
T38174553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon a 2 |
E1000168
|
entity |
| Predicate | usesRoyalTheme |
P190747
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Canon a 2, usesRoyalTheme, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoyalTheme Context triple: [Canon a 2, usesRoyalTheme, true]
-
A.
hasRoyalSymbol
Indicates that an entity possesses or is associated with a symbol representing royalty or royal authority.
-
B.
usesThemeBy
Indicates that one entity incorporates, applies, or is based on a theme that was created, defined, or provided by another entity.
-
C.
royalUse
Indicates that something is used, employed, or reserved specifically by or for a royal person or royal institution.
-
D.
hasRoyalCircle
Indicates that an entity belongs to, is part of, or is associated with a royal or monarch’s inner circle or court.
-
E.
usedAsRoyalFavor
Indicates that something is employed or granted as a token of royal favor, privilege, or goodwill from a monarch or ruling authority.
- F. None of above. chosen
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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: May 3, 2026, 4:29 p.m.