Triple
T27682753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Kilian |
E697948
|
entity |
| Predicate | hasLatinNameForm |
P76738
|
FINISHED |
| Object | Saint Kilianus |
—
|
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: Saint Kilianus | Statement: [Saint Kilian, hasLatinNameForm, Saint Kilianus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatinNameForm Context triple: [Saint Kilian, hasLatinNameForm, Saint Kilianus]
-
A.
hasLatinName
Indicates that an entity is associated with a specific Latin (scientific) name.
-
B.
hasLatinizedName
chosen
Indicates that an entity is associated with a version of its name that has been converted into Latin form or spelling.
-
C.
hasOfficialNameInLatin
Indicates that an entity has an official or formally recognized name expressed in the Latin language.
-
D.
hasLatinNameMeaning
Indicates that an entity’s Latin name conveys a specific meaning or refers to a particular concept.
-
E.
hasLatinAdjectiveForm
Indicates that an entity has a corresponding adjectival form in Latin derived from its name or designation.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 27, 2026, 2:47 p.m.