Triple
T24465233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universitas Granatensis |
E616947
|
entity |
| Predicate | usesLatinNameHistorically |
P97178
|
FINISHED |
| Object | Universitas Granatensis |
—
|
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: Universitas Granatensis | Statement: [Universitas Granatensis, usesLatinNameHistorically, Universitas Granatensis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLatinNameHistorically Context triple: [Universitas Granatensis, usesLatinNameHistorically, Universitas Granatensis]
-
A.
historicalNameInLatin
chosen
Indicates that an entity has a historically used name expressed in Latin.
-
B.
hasLatinName
Indicates that an entity is associated with a specific Latin (scientific) name.
-
C.
hasLatinizedName
Indicates that an entity is associated with a version of its name that has been converted into Latin form or spelling.
-
D.
languageOfHistoricName
Indicates the language in which a historic or former name of an entity is expressed.
-
E.
hasOfficialNameInLatin
Indicates that an entity has an official or formally recognized name expressed in the Latin language.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298cd2a748190bbb4634e879d89f2 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.