Triple
T4992308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stridon |
E112159
|
entity |
| Predicate | languageInHistoricalContext |
P30358
|
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: [Stridon, languageInHistoricalContext, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageInHistoricalContext Context triple: [Stridon, languageInHistoricalContext, Latin]
-
A.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
B.
languageOfHistoricalRecord
chosen
Indicates the language in which a given historical record is written or recorded.
-
C.
historicalLanguageOfEnvironment
Indicates that a language was historically used or prevalent in a given environment or setting, even if it is not the current primary language there.
-
D.
historicalLanguageInfluenceOn
Indicates that one language has had a shaping or contributory effect on the development, vocabulary, structure, or usage of another language over time.
-
E.
historicalLanguageCenter
Indicates that a location has served as a significant hub or focal point for the development, use, or study of a particular language in the past.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.