Triple
T8780669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jędrzejów |
E208715
|
entity |
| Predicate | hasNearbyLandscapeType |
P85343
|
FINISHED |
| Object | upland |
—
|
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: upland | Statement: [Jędrzejów, hasNearbyLandscapeType, upland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyLandscapeType Context triple: [Jędrzejów, hasNearbyLandscapeType, upland]
-
A.
hasNearbyForestType
Indicates that one entity is located close to, or in the vicinity of, a forest of a specified type.
-
B.
hasNearbyHabitats
Indicates that one entity has other habitats located close to it in geographic or spatial terms.
-
C.
hasNearbyPlateau
Indicates that one geographic entity is located close to or adjacent to a plateau.
-
D.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
E.
hasNearbyTownType
Indicates that one entity has, in its vicinity, a town of a specified type or classification.
- 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_69ca835fbee88190bf625939bac48d7f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f55b7b08190ab3e18cd634a144b |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:42 p.m.