Triple
T6842826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan |
E157814
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Ioan |
E208142
|
NE 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: Ioan | Statement: [Ivan, hasCognate, Ioan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ioan Context triple: [Ivan, hasCognate, Ioan]
-
A.
Ioan
chosen
Ioan is a given name, commonly used in Romanian and other Eastern European languages, that corresponds to the English name John.
-
B.
Joannes
Joannes was a late Western Roman usurper-emperor who briefly ruled from 423 to 425 AD before being overthrown by forces loyal to the Theodosian dynasty.
-
C.
Matthaeus
Matthaeus is the Latin form of the given name Matthew, commonly associated with the biblical apostle and evangelist.
-
D.
Damianus
Damianus is a Latinized given name historically used in ecclesiastical and scholarly contexts, closely related to the name Damian.
-
E.
Petrus
Petrus is the Latin form of the name Peter, historically used in religious and classical contexts and serving as the root for various European given names.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b5f7648190ad8561caeb678932 |
completed | March 27, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c72fb9a8c08190993807f1a4c54184 |
completed | March 28, 2026, 1:32 a.m. |
Created at: March 27, 2026, 2:19 p.m.