Triple
T8096149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valbo Church |
E188990
|
entity |
| Predicate | isCentralPlaceFor |
P164
|
FINISHED |
| Object | local Lutheran congregation |
—
|
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: local Lutheran congregation | Statement: [Valbo Church, isCentralPlaceFor, local Lutheran congregation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralPlaceFor Context triple: [Valbo Church, isCentralPlaceFor, local Lutheran congregation]
-
A.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
-
B.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
C.
isHomeOf
Indicates that a place serves as the primary residence or base for a person, group, or organization.
-
D.
isMajorCenterOf
chosen
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
E.
locatedInHubOf
Indicates that one entity is situated within the central hub or core area associated with 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4291f1d4819098985ac2b20b6c75 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.