Triple
T8345159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augusta |
E196016
|
entity |
| Predicate | signified |
P129
|
FINISHED |
| Object | imperial dignity |
—
|
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: imperial dignity | Statement: [Augusta, signified, imperial dignity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signified Context triple: [Augusta, signified, imperial dignity]
-
A.
signaled
Indicates that one entity communicated a message, warning, or instruction to another through a deliberate signal or cue.
-
B.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
C.
significance
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
-
D.
hasParticularSignificanceFor
Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
-
E.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
- 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7feef7e8819084ca0441d146bac7 |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:58 p.m.