Triple
T8379501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abjad numerals |
E197653
|
entity |
| Predicate | hasOrderingVariant |
P1109
|
FINISHED |
| Object | Levantine abjad order |
—
|
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: Levantine abjad order | Statement: [Abjad numerals, hasOrderingVariant, Levantine abjad order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderingVariant Context triple: [Abjad numerals, hasOrderingVariant, Levantine abjad order]
-
A.
hasOrder
chosen
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
B.
hasSVOOrder
Indicates that a language or construction follows a basic word order where the subject comes first, followed by the verb, and then the object.
-
C.
hasSVOAlternativeOrder
Indicates that there exists an alternative Subject–Verb–Object word order for expressing the same proposition or relation.
-
D.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
E.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c3dc1881908081c6a2829deb5a |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.