Triple
T16053169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Bernard |
E389405
|
entity |
| Predicate | ancestralType |
P116143
|
FINISHED |
| Object | Alpine mastiff-type dogs |
—
|
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: Alpine mastiff-type dogs | Statement: [St Bernard, ancestralType, Alpine mastiff-type dogs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralType Context triple: [St Bernard, ancestralType, Alpine mastiff-type dogs]
-
A.
ancestralStatus
Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
-
B.
typeOfAncestry
chosen
Indicates that one entity’s ancestry or lineage is characterized as being of a particular type or origin in relation to another entity.
-
C.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
D.
ancestralRange
Indicates the geographic area or region that a lineage or taxon historically occupied in its evolutionary past.
-
E.
ancestralLinks
Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.