Triple
T9582978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomasz |
E231217
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Tomas |
E143480
|
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: Tomas | Statement: [Tomasz, relatedName, Tomas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tomas Context triple: [Tomasz, relatedName, Tomas]
-
A.
Tomas
chosen
Tomas is a masculine given name commonly used in various European and Latin American countries, often equivalent to "Thomas" in English.
-
B.
Tomáš
Tomáš is a masculine given name commonly used in Czech and Slovak cultures, equivalent to Thomas in English.
-
C.
Tomasino
Tomasino is the colloquial term used to refer to students of the University of Santo Tomas in the Philippines.
-
D.
Tobias
Tobias is the virtuous young protagonist of the biblical Book of Tobit, known for his journey with the angel Raphael and the healing of his father’s blindness.
-
E.
Tobias
Tobias is a character from the novel "Watch Over Me," playing a significant role in the story's emotional and psychological development.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99cebaf081908033536a53fbf668 |
completed | April 1, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d189ef34c48190974a1a4ca6943a87 |
completed | April 4, 2026, 10 p.m. |
Created at: March 30, 2026, 8:05 p.m.