Triple
T19978772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gautar |
E493759
|
entity |
| Predicate | ethnonymRoot |
P138138
|
FINISHED |
| Object | Proto-Germanic *Gautaz |
—
|
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: Proto-Germanic *Gautaz | Statement: [Gautar, ethnonymRoot, Proto-Germanic *Gautaz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnonymRoot Context triple: [Gautar, ethnonymRoot, Proto-Germanic *Gautaz]
-
A.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
B.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
-
C.
ethnonymSingular
Indicates that the subject is the singular form of an ethnonym (a name for a member of a specific ethnic or national group).
-
D.
ethnonymInLanguage
Indicates that a given term is the name used in a specified language to refer to the people of a particular ethnic group or nationality.
-
E.
ethnonymPlural
Indicates the plural form of an ethnonym, expressing how the name of a people or ethnic group is written when referring to multiple members.
- F. None of above. chosen
Provenance (4 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d11108481908241a2a96a795a7d |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:27 p.m.