Triple
T7641814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibn Battuta |
E173026
|
entity |
| Predicate | documentedSindh |
P55104
|
FINISHED |
| Object | in his Rihla |
—
|
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: in his Rihla | Statement: [Ibn Battuta, documentedSindh, in his Rihla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentedSindh Context triple: [Ibn Battuta, documentedSindh, in his Rihla]
-
A.
populationRankInSindh
Indicates the relative position of an entity in terms of population size compared to other entities within Sindh.
-
B.
distanceFromKarachi
Indicates the measured spatial distance between a given entity’s location and the city of Karachi.
-
C.
historicallyDocumentedBy
chosen
Indicates that information about an entity or event is recorded or attested in a specific historical document or source.
-
D.
statusInPakistan
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Pakistan.
-
E.
regionOfArchaeologicalSurvey
Indicates the geographic area within which an archaeological survey has been conducted or is intended to take place.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6facefbe08190882bd76cf3cd605e |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:58 p.m.