Triple
T32794519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aa (Auricher Tief) |
E838720
|
entity |
| Predicate | isInRegionWithCharacteristic |
P274
|
FINISHED |
| Object | marshy lowlands |
—
|
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: marshy lowlands | Statement: [Aa (Auricher Tief), isInRegionWithCharacteristic, marshy lowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInRegionWithCharacteristic Context triple: [Aa (Auricher Tief), isInRegionWithCharacteristic, marshy lowlands]
-
A.
occursInDeviceRegion
Indicates that an event or process takes place within a specified region or area of a device.
-
B.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
C.
isKeyRegionIn
Indicates that a region plays a central or strategically important role within a larger area, system, or context.
-
D.
meetsInRegion
Indicates that two or more entities encounter or come together within a specified geographic or spatial region.
-
E.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:14 a.m.