Triple
T13604714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People of the Ditch |
E325030
|
entity |
| Predicate | hasSourceLanguageTerm |
P8506
|
FINISHED |
| Object | أخدود (ukhdud) |
—
|
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: أخدود (ukhdud) | Statement: [People of the Ditch, hasSourceLanguageTerm, أخدود (ukhdud)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceLanguageTerm Context triple: [People of the Ditch, hasSourceLanguageTerm, أخدود (ukhdud)]
-
A.
hasLinguisticClassificationSource
Indicates the source or reference from which a linguistic classification has been derived or documented.
-
B.
sourceLanguageMeaning
chosen
Indicates that one entity expresses the meaning or sense of another entity in a particular source language.
-
C.
languageTranslatedFrom
Indicates that a language is the source/original language from which content has been translated into another language.
-
D.
hasLexiconSource
Indicates that a lexical item or entry is derived from, documented in, or otherwise sourced from a particular lexicon or lexical resource.
-
E.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.