Triple
T26930853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ali Murad |
E678212
|
entity |
| Predicate | presentDayProvinceOfRealm |
P31240
|
FINISHED |
| Object | Sindh |
—
|
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: Sindh | Statement: [Ali Murad, presentDayProvinceOfRealm, Sindh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayProvinceOfRealm Context triple: [Ali Murad, presentDayProvinceOfRealm, Sindh]
-
A.
presentDayProvince
chosen
Indicates that one entity is the present-day administrative province in which the other entity is currently located or to which it now belongs.
-
B.
presentDayTerritoryOf
Indicates that one entity is the modern-day territorial equivalent or current geographic area corresponding to another (typically historical) entity.
-
C.
presentDayCityRegion
Indicates that a city is located within or associated with a particular region in the present day.
-
D.
presentDayRegionName
Indicates the current or modern geographic region in which an entity or location is situated or identified.
-
E.
administrativeDivisionToday
Indicates that one entity currently functions as an administrative subdivision or jurisdictional unit within the other.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 6:12 a.m.