Triple
T29423503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James II of Scotland |
E746217
|
entity |
| Predicate | hasEpiphet |
P121211
|
FINISHED |
| Object | James of the Fiery Face |
—
|
NE NERFINISHED |
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: James of the Fiery Face | Statement: [James II of Scotland, hasEpiphet, James of the Fiery Face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpiphet Context triple: [James II of Scotland, hasEpiphet, James of the Fiery Face]
-
A.
hasEpitomeBy
Indicates that something is represented, summarized, or exemplified by a particular epitome (a concise or quintessential representation of it).
-
B.
epithetAppliedBy
Indicates that a particular epithet or descriptive label is used or assigned by a specific agent to a target entity.
-
C.
associatedWithEpithet
chosen
Indicates that an entity is linked to or described by a particular epithet or descriptive label.
-
D.
hasMeaningOfEpithet
Indicates that one entity expresses or conveys the meaning or sense of another entity’s epithet.
-
E.
hasPoeticEpigraphs
Indicates that one entity (typically a work) includes poetic epigraphs associated with or prefacing another entity.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a6aa3d08190887bfa4eed48faeb |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:07 p.m.