Triple
T6012385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharraqa |
E133865
|
entity |
| Predicate | hasTopographicalContext |
P53384
|
FINISHED |
| Object | riverine settlement |
—
|
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: riverine settlement | Statement: [Maharraqa, hasTopographicalContext, riverine settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopographicalContext Context triple: [Maharraqa, hasTopographicalContext, riverine settlement]
-
A.
hasTopographicContext
chosen
Indicates that one entity is related to or characterized by a particular topographic or physical landscape context.
-
B.
hasTopographicalRole
Indicates that an entity serves a specific functional or positional role within a topographical or spatial context.
-
C.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
-
D.
elevationContext
Indicates the contextual relationship between an entity and its elevation or vertical position relative to a reference point or environment.
-
E.
topographicMap
Indicates a mapping relationship where a representation shows the physical terrain features and elevation contours of a geographic area.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f528acc8190bc6943d812460b57 |
completed | March 22, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.