Triple
T561749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runic alphabet |
E13465
|
entity |
| Predicate | notableCorpus |
P5301
|
FINISHED |
| Object | runestones |
—
|
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: runestones | Statement: [Runic alphabet, notableCorpus, runestones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCorpus Context triple: [Runic alphabet, notableCorpus, runestones]
-
A.
notableText
Indicates that a particular piece of text is especially significant, prominent, or worthy of attention in relation to the associated entity or context.
-
B.
notableManager
Indicates that an entity has, or is associated with, a manager who is particularly prominent, distinguished, or widely recognized.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableRobot
Indicates that the subject is a robot recognized for its significance, prominence, or special distinction.
-
E.
notedIn
chosen
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a700e608190b235246df057bd9b |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494befb8481908bb4e2e9f31e343b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.