Triple
T8015372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryan |
E186599
|
entity |
| Predicate | etymologicalFamily |
P42488
|
FINISHED |
| Object | Celtic names |
—
|
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: Celtic names | Statement: [Bryan, etymologicalFamily, Celtic names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologicalFamily Context triple: [Bryan, etymologicalFamily, Celtic names]
-
A.
etymologicalLanguageFamily
chosen
Indicates that one entity is the language family from which the other entity is etymologically derived or historically originates.
-
B.
etymologicalForm
Indicates that one linguistic form is derived from, or historically originates in, another form as its etymological source.
-
C.
etymologyRelatesTo
Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
-
D.
etymologicalField
Indicates that one term belongs to a particular semantic or conceptual domain relevant to its etymological origin or historical development.
-
E.
sharesLinguisticFamilyWith
Indicates that two languages belong to the same linguistic family or branch within a language family.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df24e4c8190ae1c46e97e54787d |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.