Triple
T27288498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imad |
E688547
|
entity |
| Predicate | isPersonalNameIn |
P162309
|
FINISHED |
| Object | Saudi Arabia |
—
|
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: Saudi Arabia | Statement: [Imad, isPersonalNameIn, Saudi Arabia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPersonalNameIn Context triple: [Imad, isPersonalNameIn, Saudi Arabia]
-
A.
isPersonalNameIn
chosen
Indicates that a personal name appears within or is contained in a specified context, such as a document, text span, or dataset.
-
B.
isPersonalName
Indicates that the value is a personal name identifying an individual person.
-
C.
hasNoPersonalNameIn
Indicates that an entity lacks a specific personal name within a given context, language, or naming system.
-
D.
isGivenName
Indicates that one entity is the personal (given) name of another entity.
-
E.
usesPersonalNamesFrom
Indicates that one entity employs or adopts the system or set of personal names originating from another entity.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 11:13 a.m.