Triple
T897282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aramaic |
E19371
|
entity |
| Predicate | stillSpokenIn |
P4250
|
FINISHED |
| Object | some communities in Syria |
—
|
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: some communities in Syria | Statement: [Aramaic, stillSpokenIn, some communities in Syria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillSpokenIn Context triple: [Aramaic, stillSpokenIn, some communities in Syria]
-
A.
areSpokenIn
Indicates that a particular language is used as a spoken means of communication within a specified region, community, or context.
-
B.
isSpokenAs
Indicates that one entity is used as the spoken or verbal form of another entity (e.g., a word, name, or phrase).
-
C.
isWidelySpokenIn
Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
-
D.
isScheduledLanguageOf
Indicates that a particular language is officially planned or designated to be used for a specific event, program, or context.
-
E.
spokenByMinorityIn
chosen
Indicates that a language or dialect is used primarily by a minority group within a specified geographic or political region.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad2550c88190a624eb5627d472ad |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9635608190a297e2067b8dcee2 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.