Triple
T10531353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Syriac script |
E248446
|
entity |
| Predicate | ISO15924 |
P11937
|
FINISHED |
| Object | Syrc |
E727945
|
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: Syrc | Statement: [West Syriac script, ISO15924, Syrc]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Syrc Context triple: [West Syriac script, ISO15924, Syrc]
-
A.
Syrc
chosen
Syrc is the ISO 15924 four-letter code that designates the Syriac script used for writing various dialects of the Syriac language.
-
B.
Syrkin
Syrkin is a Jewish surname most notably associated with Nachman Syrkin, a pioneering theorist of socialist Zionism.
-
C.
Sybic
Sybic is a class of German electric locomotives used primarily for passenger and freight services.
-
D.
Syrdon
Syrdon is a cunning and often mischievous trickster figure from the Caucasian Nart sagas, known for his wit, guile, and disruptive antics among the Nart heroes.
-
E.
SYR
SYR is the three-letter ISO 3166-1 alpha-3 country code representing the Middle Eastern nation of Syria.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a16915c8190ac4f3fd5e43c5fed |
completed | April 7, 2026, 1:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d90e471e9c8190b134249073b289bd |
completed | April 10, 2026, 2:50 p.m. |
Created at: April 6, 2026, 12:30 p.m.