Triple
T33191885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chronicon Syriacum |
E849630
|
entity |
| Predicate | hasCriticalEditions |
P187401
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chronicon Syriacum, hasCriticalEditions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCriticalEditions Context triple: [Chronicon Syriacum, hasCriticalEditions, yes]
-
A.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
B.
usedInCriticalEditions
Indicates that something (such as a text, source, or variant) is employed as authoritative material in the preparation of critical editions.
-
C.
hasPublishedEditions
Indicates that an entity (such as a work or publication) has one or more specific editions that have been published.
-
D.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
E.
hasSerializedEditions
Indicates that an entity has one or more serialized editions or installments derived from it.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 1, 2026, 1:29 a.m.