Triple
T16460375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyss |
E399789
|
entity |
| Predicate | isResidentialTownInRegion |
P5065
|
FINISHED |
| Object | greater Bern area |
—
|
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: greater Bern area | Statement: [Lyss, isResidentialTownInRegion, greater Bern area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResidentialTownInRegion Context triple: [Lyss, isResidentialTownInRegion, greater Bern area]
-
A.
isResidentialTown
Indicates that a town is primarily used or designated for residential living rather than for commercial, industrial, or other primary purposes.
-
B.
isResidentialSuburbOf
chosen
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
-
C.
isResidentialBaseFor
Indicates that a location serves as the primary place of residence or home base for a person or group.
-
D.
hasResidentialArea
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
E.
isSuburbanResidentialArea
Indicates that a location is primarily a residential neighborhood situated in a suburban (non-urban, non-rural) setting.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d80e66c8190b2b3199efe9cfaa1 |
completed | April 18, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.