Triple
T6099956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruritania |
E135967
|
entity |
| Predicate | hasCourtCulture |
P15786
|
FINISHED |
| Object | aristocratic court |
—
|
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: aristocratic court | Statement: [Ruritania, hasCourtCulture, aristocratic court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtCulture Context triple: [Ruritania, hasCourtCulture, aristocratic court]
-
A.
courtCulture
chosen
Indicates the prevailing norms, practices, and behavioral expectations that characterize how a particular court operates and conducts its proceedings.
-
B.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
C.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
D.
hasCulturalExpression
Indicates that an entity embodies, manifests, or is associated with a particular cultural form, practice, or expression.
-
E.
hasCulturalWing
Indicates that an entity includes or is associated with a dedicated cultural wing or section as part of its structure or facilities.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3970808190ba90f5e4235db9f2 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.