Triple
T30162801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tungri |
E766712
|
entity |
| Predicate | ethnicNameAttestedIn |
P60488
|
FINISHED |
| Object | Latin inscriptions |
—
|
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: Latin inscriptions | Statement: [Tungri, ethnicNameAttestedIn, Latin inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicNameAttestedIn Context triple: [Tungri, ethnicNameAttestedIn, Latin inscriptions]
-
A.
ethnonymAttestedIn
chosen
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
-
B.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
C.
isEthnonymFor
Indicates that one term is the ethnonym (name of a people or ethnic group) used to refer to another entity.
-
D.
ethnonymRoot
Indicates that one term serves as the morphological or etymological root from which an ethnonym (a name for an ethnic group or people) is derived.
-
E.
ethnicEponymOf
Indicates that one term is an eponym derived from or naming an ethnic group or people.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 7:22 p.m.