Triple
T35055443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HY |
E1011448
|
entity |
| Predicate | registrationLocation |
P158771
|
FINISHED |
| Object | Hyvinkää |
—
|
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: Hyvinkää | Statement: [HY, registrationLocation, Hyvinkää]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationLocation Context triple: [HY, registrationLocation, Hyvinkää]
-
A.
inscriptionLocation
Indicates the place or surface on which an inscription is written or engraved.
-
B.
reportedLocation
chosen
Indicates that an entity has been specified or recorded as being at a particular location, typically based on a report or observation rather than direct verification.
-
C.
connectionLocation
Indicates the place or spatial context where a connection between entities occurs or is established.
-
D.
membershipLocation
Indicates that an entity’s membership or affiliation is associated with, based in, or held at a particular location.
-
E.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.