Triple
T31452192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Aramaic |
E802352
|
entity |
| Predicate | neighboringBranch |
P91908
|
FINISHED |
| Object | Western Aramaic |
—
|
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: Western Aramaic | Statement: [Central Aramaic, neighboringBranch, Western Aramaic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringBranch Context triple: [Central Aramaic, neighboringBranch, Western Aramaic]
-
A.
siblingBranch
chosen
Indicates that two branches share the same immediate parent node in a hierarchical structure, making them parallel or peer branches.
-
B.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
-
C.
neighboringTo
Indicates that one entity is located directly adjacent or very close to another entity, sharing a common boundary or immediate vicinity.
-
D.
neighboringBloc
Indicates that two political or geographic blocs share a common border or are directly adjacent to each other.
-
E.
neighboringBlockNext
Indicates that one block is directly adjacent to and immediately follows another block in the spatial or ordered layout.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 30, 2026, 9:14 p.m.