Triple
T30071913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miróbriga |
E764205
|
entity |
| Predicate | ancientLanguageOfName |
P143350
|
FINISHED |
| Object | Latin |
—
|
NE NERFINISHED |
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 | Statement: [Miróbriga, ancientLanguageOfName, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancientLanguageOfName Context triple: [Miróbriga, ancientLanguageOfName, Latin]
-
A.
ancientNameMeaning
Indicates that an entity’s ancient or historical name carries a particular meaning or interpretation.
-
B.
languageOfNamesake
Indicates the language in which the namesake of an entity (such as a person, place, or object) is named or expressed.
-
C.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
D.
hasNameEtymologyIn
chosen
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.
-
E.
hasAncientEthnicName
Indicates that an entity is associated with an ethnic name or designation that originates from ancient times.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d386a3c81909cb643a9140701ea |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:01 p.m.