Triple
T35707737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayn al-Jarr |
E1031763
|
entity |
| Predicate | hasNameEtymologicalRelationTo |
P108324
|
FINISHED |
| Object | Anjar |
—
|
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: Anjar | Statement: [Ayn al-Jarr, hasNameEtymologicalRelationTo, Anjar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameEtymologicalRelationTo Context triple: [Ayn al-Jarr, hasNameEtymologicalRelationTo, Anjar]
-
A.
etymologyRelatesTo
Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
-
B.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
C.
hasEtymologicalBasis
Indicates that one term, name, or expression is derived from, based on, or historically formed from the other in terms of linguistic origin.
-
D.
nameCognateOf
Indicates that two names share a common linguistic origin or form, typically due to derivation from the same root or historical source.
-
E.
etymologicalRootName
chosen
Indicates that one name is derived from, or originates etymologically in, another name.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:05 p.m.