Triple
T25713981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-358 |
E644807
|
entity |
| Predicate | successorNameInTurkishService |
P151852
|
FINISHED |
| Object | TCG Gelibolu |
—
|
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: TCG Gelibolu | Statement: [D-358, successorNameInTurkishService, TCG Gelibolu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorNameInTurkishService Context triple: [D-358, successorNameInTurkishService, TCG Gelibolu]
-
A.
successorNameInGreekService
Indicates that the predicate specifies the name of a successor as used or rendered in a Greek-language service or context.
-
B.
nameInTurkish
Indicates that an entity is known or referred to by a specific name in the Turkish language.
-
C.
successorNameForm
Indicates that the object is the name or naming form used for the successor entity that follows the subject in a sequence or lineage.
-
D.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
-
E.
successorNameInService
chosen
Indicates that one entity is the name of the successor that takes over a role, position, or function within a particular service or service context.
- F. None of above.
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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 21, 2026, 9:22 p.m.