Triple
T31099111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Naysaburi |
E792620
|
entity |
| Predicate | refersToPeopleFrom |
P53228
|
FINISHED |
| Object | Nishapur |
—
|
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: Nishapur | Statement: [al-Naysaburi, refersToPeopleFrom, Nishapur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToPeopleFrom Context triple: [al-Naysaburi, refersToPeopleFrom, Nishapur]
-
A.
refersToPersonFrom
chosen
Indicates that one entity makes reference to, mentions, or is about a person originating from or associated with a particular place or group.
-
B.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
C.
refersToPersonKnownFor
Indicates that one entity makes reference to a person who is notable or recognized for some specific role, achievement, or characteristic.
-
D.
depictsPeopleFrom
Indicates that one entity visually represents or portrays people originating from or associated with another entity.
-
E.
referredToBy
Indicates that one entity is mentioned, cited, or identified by another entity as a reference to it.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 29, 2026, 9:03 p.m.