Triple
T16600521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italic |
E403317
|
entity |
| Predicate | majorClassicalLanguage |
P6519
|
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: [Italic, majorClassicalLanguage, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorClassicalLanguage Context triple: [Italic, majorClassicalLanguage, Latin]
-
A.
mainClassicalLanguage
chosen
Indicates the primary classical (historically foundational) language associated with an entity, such as a text, culture, or scholarly tradition.
-
B.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
C.
recognizedAsClassicalLanguageBy
Indicates that an entity is acknowledged or designated by a specified authority or source as a classical language.
-
D.
majorStandardLanguage
Indicates that a language is the primary or most widely used standard language associated with an entity (such as a country, region, or group).
-
E.
classicalLanguageOfIndia
Indicates that the subject is a language that is formally recognized as a classical language of India.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d75772c8190b02aef02ea6788e1 |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.