Triple
T34270631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emericus |
E879303
|
entity |
| Predicate | usedAsLatinNameOf |
P71235
|
FINISHED |
| Object | Hungarian individuals named Imre |
—
|
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: Hungarian individuals named Imre | Statement: [Emericus, usedAsLatinNameOf, Hungarian individuals named Imre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsLatinNameOf Context triple: [Emericus, usedAsLatinNameOf, Hungarian individuals named Imre]
-
A.
hasLatinName
Indicates that an entity is associated with a specific Latin (scientific) name.
-
B.
eraNameUsedInDocuments
Indicates that a particular era name is used as a temporal reference in the specified documents.
-
C.
hasOfficialNameInLatin
Indicates that an entity has an official or formally recognized name expressed in the Latin language.
-
D.
oftenUsedAsNameFor
chosen
Indicates that something frequently serves as a name or designation for another entity.
-
E.
hasLatinNameMeaning
Indicates that an entity’s Latin name conveys a specific meaning or refers to a particular concept.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 1, 2026, 1:56 a.m.