Triple
T38556241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teodorito |
E925251
|
entity |
| Predicate | derivedFromTheophoricName |
P191187
|
FINISHED |
| Object | Theodoros |
—
|
NE NERFINISHED |
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: Theodoros | Statement: [Teodorito, derivedFromTheophoricName, Theodoros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromTheophoricName Context triple: [Teodorito, derivedFromTheophoricName, Theodoros]
-
A.
isTheophoric
Indicates that something (typically a name or term) incorporates the name of a deity or refers explicitly to a god.
-
B.
hasTheophoricPlaceName
Indicates that a place bears a name derived from or incorporating the name of a deity.
-
C.
familyNameDerivedFrom
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
-
D.
dynasticNameDerivedFrom
Indicates that a dynastic name is derived from, or based on, another name, title, or source.
-
E.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
- F. None of above. chosen
Provenance (4 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.