Triple
T2843733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dahab |
E62531
|
entity |
| Predicate | localCommunity |
P6194
|
FINISHED |
| Object | Bedouin tribes |
—
|
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: Bedouin tribes | Statement: [Dahab, localCommunity, Bedouin tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localCommunity Context triple: [Dahab, localCommunity, Bedouin tribes]
-
A.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
B.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
C.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
D.
community
chosen
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
E.
notableCityCommunity
Indicates a relationship where a city is notably associated with, recognized by, or significantly connected to a particular community.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf1a07508190be35fe85733ddeed |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.