Triple
T29768610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doradus |
E753985
|
entity |
| Predicate | isGenitiveFormInLanguage |
P153547
|
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: [Doradus, isGenitiveFormInLanguage, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGenitiveFormInLanguage Context triple: [Doradus, isGenitiveFormInLanguage, Latin]
-
A.
latinGenitive
chosen
Indicates that one entity is in the Latin genitive case in relation to another, typically expressing possession, origin, or association.
-
B.
iauGenitive
Indicates a genitive (possessive or belonging) relationship between two entities, where one is owned by, associated with, or derived from the other.
-
C.
hasGrammaticalGender
Indicates that one entity assigns or possesses a specific grammatical gender in relation to another entity (such as a word, phrase, or linguistic unit).
-
D.
grammaticalForm
Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
-
E.
hasCaseForms
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6745f8354819085a81de5c32dd49e |
completed | May 2, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:40 p.m.