Triple
T15099576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apprentice Pillar |
E360626
|
entity |
| Predicate | hasLegendMotive |
P65262
|
FINISHED |
| Object | master’s jealousy of apprentice’s superior work |
—
|
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: master’s jealousy of apprentice’s superior work | Statement: [Apprentice Pillar, hasLegendMotive, master’s jealousy of apprentice’s superior work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendMotive Context triple: [Apprentice Pillar, hasLegendMotive, master’s jealousy of apprentice’s superior work]
-
A.
legendaryMotive
Indicates a motive or driving reason behind an action or state that is regarded as legendary, iconic, or of mythic significance.
-
B.
hasMotiveTheme
chosen
Indicates that an action, event, or situation is associated with a central motivating theme or underlying driving idea.
-
C.
hasLegendAssociatedWith
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
D.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an entity.
-
E.
mottoLegend
Indicates that a text serves as a motto or slogan associated with a particular legend or explanatory note.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0054f00388190a5123d9f4a869b96 |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.