Triple
T11915918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwardian court |
E283519
|
entity |
| Predicate | hasChivalricCulture |
P3114
|
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: [Edwardian court, hasChivalricCulture, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChivalricCulture Context triple: [Edwardian court, hasChivalricCulture, true]
-
A.
chivalricTradition
Indicates a relationship where behaviors, values, or actions conform to or are guided by the codes and ideals of chivalry.
-
B.
showsAttitudeTowardChivalry
Indicates that an entity expresses or demonstrates a particular stance, feeling, or evaluation regarding chivalry.
-
C.
hasCavalryHeritage
Indicates that an entity has a historical or traditional connection to cavalry forces or mounted military service.
-
D.
hasCulturalLegacyIn
Indicates that an entity has left a lasting cultural influence, impact, or heritage within a particular place, community, or cultural context.
-
E.
hasCulturalFeature
chosen
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8deb14881909b65a1f159aec65f |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.