Triple
T28368960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Edward Stuart |
E718570
|
entity |
| Predicate | folkFigureIn |
P131560
|
FINISHED |
| Object | Scottish culture |
—
|
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: Scottish culture | Statement: [Charles Edward Stuart, folkFigureIn, Scottish culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: folkFigureIn Context triple: [Charles Edward Stuart, folkFigureIn, Scottish culture]
-
A.
folkloreCharacter
chosen
Indicates that one entity is a character originating from the traditional stories, myths, or legends associated with the other entity.
-
B.
typicalFigure
Indicates that one entity serves as a standard or representative example (a typical instance) of the other entity.
-
C.
featuresFigureOf
Indicates that one entity includes or presents another entity as a figure, illustration, or visual element.
-
D.
associatedLegendaryFigure
Indicates that an entity is traditionally linked or connected to a particular legendary or mythological figure.
-
E.
mythologicalFigureFeatured
Indicates that a mythological figure is prominently depicted, referenced, or plays a significant role within a given work, context, or medium.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c582da481909a86d6f72b452ad7 |
completed | May 2, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:58 a.m.