Triple
T28218973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runaway Horses |
E711396
|
entity |
| Predicate | exploresSamuraiEthos |
P163686
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Runaway Horses, exploresSamuraiEthos, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresSamuraiEthos Context triple: [Runaway Horses, exploresSamuraiEthos, yes]
-
A.
notableSamurai
Indicates that the subject is recognized as a samurai of particular historical, cultural, or martial significance.
-
B.
chivalricTradition
Indicates a relationship where behaviors, values, or actions conform to or are guided by the codes and ideals of chivalry.
-
C.
focusesOnVirtue
chosen
Indicates that an action, practice, or concept is primarily concerned with cultivating or emphasizing moral virtue or virtuous character.
-
D.
hasVirtueInTradition
Indicates that an entity possesses or exemplifies a particular virtue as understood within a specified cultural, religious, or philosophical tradition.
-
E.
showsAttitudeTowardChivalry
Indicates that an entity expresses or demonstrates a particular stance, feeling, or evaluation regarding chivalry.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 10:45 p.m.