Triple
T5287761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Grace |
E119663
|
entity |
| Predicate | traditional |
P60439
|
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: [His Grace, traditional, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditional Context triple: [His Grace, traditional, true]
-
A.
traditionalEnd
Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
-
B.
traditionalStyle
chosen
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
C.
traditionalCountry
Indicates that a country is characterized by long-established customs, cultural practices, and social norms that have been preserved over time.
-
D.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
-
E.
traditionalFocus
Indicates a focus on preserving, emphasizing, or adhering to long-established customs, practices, or conventions within a given context.
- 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.