Triple
T3686812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebastián |
E78243
|
entity |
| Predicate | derivedFrom |
P909
|
FINISHED |
| Object | Sebastianus |
E57255
|
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: Sebastianus | Statement: [Sebastián, derivedFrom, Sebastianus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sebastianus Context triple: [Sebastián, derivedFrom, Sebastianus]
-
A.
Sebastiano
Sebastiano is an Italian given name, commonly used as the Italian form of Sebastian.
-
B.
Sebastian
chosen
Sebastian is a masculine given name of Latin origin, commonly used in many European and English-speaking countries.
-
C.
Livias
Livias was an ancient town in the region of Perea, east of the Jordan River, known from classical and biblical-era sources.
-
D.
Marinus
Marinus is a masculine given name of Latin origin historically associated with figures such as American Revolutionary War officer Marinus Willett.
-
E.
Lucio
Lucio is a popular support hero in the game Overwatch, known for his music-based abilities that heal and speed up teammates.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4c7e2bc81909356c8b0ed90feed |
completed | March 8, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4cdeb6c288190a52e81fcbeaeec6d |
completed | March 14, 2026, 2:54 a.m. |
Created at: March 8, 2026, 3:26 p.m.