Triple
T1375813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pietro |
E29219
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Petros |
E134945
|
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: Petros | Statement: [Pietro, hasCognate, Petros]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petros Context triple: [Pietro, hasCognate, Petros]
-
A.
Petros
chosen
Petros is a Greek given name meaning "rock" or "stone," best known as the original form of the name Peter.
-
B.
Christos
Christos is the Greek term for “anointed one,” commonly used as the title “Christ” for Jesus in Christian theology.
-
C.
Linos
Linos is an alternative form of the name Linus, often associated with figures from ancient Greek mythology and early Christian tradition.
-
D.
Didymus
Didymus is another name for the Apostle Thomas, one of Jesus Christ’s twelve original disciples in the New Testament.
-
E.
Sebaste
Sebaste was an ancient city in the central highlands of Samaria, refounded and expanded by Herod the Great as a major Hellenistic-Roman urban center.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2f9b51c8190ad52fd8c151499be |
completed | March 1, 2026, 10:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acd485e7e48190b4c2dcec53ebe195 |
completed | March 8, 2026, 1:44 a.m. |
Created at: March 1, 2026, 7:59 p.m.