Triple
T38434424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Bani Bishr |
E903900
|
entity |
| Predicate | historicalAreaOfSettlement |
P203919
|
FINISHED |
| Object | southern Arabian Peninsula |
—
|
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: southern Arabian Peninsula | Statement: [Al Bani Bishr, historicalAreaOfSettlement, southern Arabian Peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalAreaOfSettlement Context triple: [Al Bani Bishr, historicalAreaOfSettlement, southern Arabian Peninsula]
-
A.
historicalPeriodOfSettlement
Indicates the historical time period during which a particular settlement or habitation of a place occurred.
-
B.
historicalSettlementType
Indicates the type or category of settlement an entity was historically classified as (e.g., village, town, city) during a past period.
-
C.
originOfSettlement
Indicates the place, source, or starting point from which a settlement was established or originated.
-
D.
modernSettlementArea
Indicates the geographic area occupied by a settlement in its modern or current form.
-
E.
historicallyASettlementOn
Indicates that one place historically existed as a settlement located on or at the site of another place.
- F. None of above. chosen
Provenance (4 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a02f10505988190be5fd57566a90e0f |
completed | May 12, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_6a02f03a8c1481909e137e270119f7ef |
completed | May 12, 2026, 9:17 a.m. |
| PDg | Predicate description generation | batch_6a02f10460a881909ed6a7159ecf1e84 |
completed | May 12, 2026, 9:21 a.m. |
Created at: May 3, 2026, 4:31 p.m.