Triple
T35341070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wałbrzych County (de facto functional center) |
E1020597
|
entity |
| Predicate | hasServiceFunctionsCenteredIn |
P105132
|
FINISHED |
| Object | Wałbrzych |
—
|
NE NERFINISHED |
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: Wałbrzych | Statement: [Wałbrzych County (de facto functional center), hasServiceFunctionsCenteredIn, Wałbrzych]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceFunctionsCenteredIn Context triple: [Wałbrzych County (de facto functional center), hasServiceFunctionsCenteredIn, Wałbrzych]
-
A.
hasServiceCenter
Indicates that an entity maintains or is associated with a service center that provides support, repair, or maintenance services.
-
B.
hasCenterIn
Indicates that something is located, based, or primarily focused within a specified central place or area.
-
C.
hasCenterFeature
Indicates that an entity possesses a specific feature or element located at its center.
-
D.
hasServiceFunction
chosen
Indicates that an entity performs, provides, or is responsible for a particular service-related function or role.
-
E.
hasCenterType
Indicates that something is characterized by or assigned a specific type or category of center.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: May 3, 2026, 4:03 p.m.