Triple
T32538668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Vosges |
E831657
|
entity |
| Predicate | hasLanguagePrimarySource |
P2925
|
FINISHED |
| Object | Latin |
—
|
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 | Statement: [Battle of Vosges, hasLanguagePrimarySource, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguagePrimarySource Context triple: [Battle of Vosges, hasLanguagePrimarySource, Latin]
-
A.
hasPrimaryLanguage1
Indicates that an entity’s main or most commonly used language is the specified language.
-
B.
languageOfSources
chosen
Indicates that the specified language is the language in which the referenced sources or source materials are expressed.
-
C.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
D.
hasPrimaryTraditionalLanguage
Indicates that one entity is the main or principal traditional language associated with another entity.
-
E.
primaryLanguageOf
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 1, 2026, 1:02 a.m.