Triple
T9476469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safahat |
E228527
|
entity |
| Predicate | laterEditionsScript |
P88326
|
FINISHED |
| Object | Latin-based Turkish alphabet |
—
|
LITERAL 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: Latin-based Turkish alphabet | Statement: [Safahat, laterEditionsScript, Latin-based Turkish alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEditionsScript Context triple: [Safahat, laterEditionsScript, Latin-based Turkish alphabet]
-
A.
laterEditionParatext
Indicates that the paratext is taken from or associated with a later edition of the work than the primary text or base edition under consideration.
-
B.
updatedEdition
Indicates that one entity is a newer or revised edition of another entity.
-
C.
modernEditionBy
Indicates that one entity is a modern edition or updated version that has been prepared, edited, or published by another entity.
-
D.
laterRepublishedWith
Indicates that an existing work was republished at a later time in a modified or updated form specified by the related entity.
-
E.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd80127744819082176b2d4417216e |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:54 p.m.