Triple
T36165923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mag Uidhir |
E1045996
|
entity |
| Predicate | originSubfamily |
P204774
|
FINISHED |
| Object | Goidelic languages |
E12686
|
NE 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: Goidelic languages | Statement: [Mag Uidhir, originSubfamily, Goidelic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originSubfamily Context triple: [Mag Uidhir, originSubfamily, Goidelic languages]
-
A.
subfamily
Indicates that one taxonomic group is a subfamily within a larger family, representing an intermediate rank in biological classification.
-
B.
belongsToSubfamily
Indicates that one entity is a member of, or classified within, a specific subfamily of another entity.
-
C.
isLargestSubfamilyOf
Indicates that one group or category is the largest subfamily within another, typically in terms of number of members or size.
-
D.
subfamilyCorrespondence
Indicates a correspondence or mapping between subfamilies, specifying how one subfamily relates or aligns to another within a broader family structure.
-
E.
subfamilyNamesakeOf
Indicates that a subfamily is named after the referenced entity, which serves as its namesake.
- F. None of above. chosen
Provenance (5 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a390d58f0f081908d047f31ef90ce34 |
completed | June 22, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:08 p.m.