Triple
T26137739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabic Extended-A |
E659427
|
entity |
| Predicate | neighborBlockPrevious |
P67239
|
FINISHED |
| Object | Arabic Extended |
—
|
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: Arabic Extended | Statement: [Arabic Extended-A, neighborBlockPrevious, Arabic Extended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighborBlockPrevious Context triple: [Arabic Extended-A, neighborBlockPrevious, Arabic Extended]
-
A.
neighboringBlockPrevious
chosen
Indicates that one block is adjacent to another block and occurs immediately before it in a defined sequence or ordering.
-
B.
neighboringBlockNext
Indicates that one block is directly adjacent to and immediately follows another block in the spatial or ordered layout.
-
C.
neighborElementPrevious
Indicates that one element is immediately preceded by another element in a sequence or structure.
-
D.
neighboringBloc
Indicates that two political or geographic blocs share a common border or are directly adjacent to each other.
-
E.
neighborElementNext
Indicates that one element is directly adjacent to and immediately follows another element in a sequence or structure.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 26, 2026, 8:18 p.m.