Triple
T5198221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neu-Anif |
E117324
|
entity |
| Predicate | hasResidentialFunctionFor |
P9421
|
FINISHED |
| Object | commuters to Salzburg |
—
|
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: commuters to Salzburg | Statement: [Neu-Anif, hasResidentialFunctionFor, commuters to Salzburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentialFunctionFor Context triple: [Neu-Anif, hasResidentialFunctionFor, commuters to Salzburg]
-
A.
hasResidentialArea
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
B.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
C.
isResidentialHubIn
chosen
Indicates that a location functions primarily as a residential center or hub within a specified larger area or region.
-
D.
isResidentialTown
Indicates that a town is primarily used or designated for residential living rather than for commercial, industrial, or other primary purposes.
-
E.
residenceUsedFor
Indicates that a particular residence is used for a specific purpose, function, or activity.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.