Triple
T13329144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Appleseed |
E317522
|
entity |
| Predicate | hasLegendaryAttribute |
P24832
|
FINISHED |
| Object | barefoot travel |
—
|
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: barefoot travel | Statement: [Johnny Appleseed, hasLegendaryAttribute, barefoot travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendaryAttribute Context triple: [Johnny Appleseed, hasLegendaryAttribute, barefoot travel]
-
A.
hasMythicMotif
chosen
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
-
B.
hasHeirloom
Indicates that one entity possesses or is associated with an heirloom originating from another entity.
-
C.
includesLegendaryCard
Indicates that an entity (such as a deck, pack, or collection) contains at least one legendary card.
-
D.
includesLegendaryForEachClass
Indicates that the set or collection contains at least one legendary instance or element corresponding to each distinct class represented.
-
E.
hasIconicArtifact
Indicates that an entity possesses or is associated with a distinctive, emblematic artifact that represents its identity, history, or significance.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.