Triple
T8514346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabulsi |
E201534
|
entity |
| Predicate | describesOrigin |
P56832
|
FINISHED |
| Object | from the city of Nablus |
—
|
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: from the city of Nablus | Statement: [Nabulsi, describesOrigin, from the city of Nablus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesOrigin Context triple: [Nabulsi, describesOrigin, from the city of Nablus]
-
A.
depictsOriginOf
Indicates that one entity visually represents or illustrates the source, beginning, or point of origin of another entity.
-
B.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
C.
alternativeOrigin
Indicates that an entity has a different or secondary source, starting point, or provenance compared to its primary or usual origin.
-
D.
physicalOrigin
chosen
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
-
E.
classOrigin
Indicates the original class or category from which an entity is derived, instantiated, or classified.
- 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe60e12848190a4a3dfa457aef275 |
completed | March 31, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:15 p.m.