Triple
T27607090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ailpín |
E700210
|
entity |
| Predicate | notableBearerContext |
P458
|
FINISHED |
| Object | Scottish royal dynasties |
—
|
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 royal dynasties | Statement: [Ailpín, notableBearerContext, Scottish royal dynasties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerContext Context triple: [Ailpín, notableBearerContext, Scottish royal dynasties]
-
A.
notableBearerDescription
Indicates that the subject has a notable bearer, with the object providing a textual description of that bearer’s significance or identity.
-
B.
notableBearerRelative
Indicates that one entity is a notable person who is related (by family or kinship) to the bearer of another entity, such as a title, name, or distinction.
-
C.
hasNotableBearer
chosen
Indicates that an entity (such as a name, title, or identifier) is borne by at least one notable person or entity.
-
D.
notableBearerExecutedBy
Indicates that a notable holder or bearer of something was executed by a specified agent or authority.
-
E.
notableBearerVariantOf
Indicates that one entity is a notable or prominent variant or version of another entity that bears or carries its characteristics.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
Created at: April 27, 2026, 2:10 p.m.