Triple
T29042635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Albert the Knight |
E738038
|
entity |
| Predicate | hasChivalricConnotation |
P55623
|
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: [King Albert the Knight, hasChivalricConnotation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChivalricConnotation Context triple: [King Albert the Knight, hasChivalricConnotation, true]
-
A.
showsAttitudeTowardChivalry
Indicates that an entity expresses or demonstrates a particular stance, feeling, or evaluation regarding chivalry.
-
B.
chivalricTradition
chosen
Indicates a relationship where behaviors, values, or actions conform to or are guided by the codes and ideals of chivalry.
-
C.
hasHeraldicAttitude
Indicates that an entity (typically an animal or figure in heraldry) is depicted with a specific standardized posture or stance in a coat of arms.
-
D.
hasAristocraticHero
Indicates that the subject work or narrative features a main hero who belongs to the aristocracy or noble class.
-
E.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 28, 2026, 10:02 a.m.