Triple
T19786948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SG |
E475293
|
entity |
| Predicate | identifiesRegistrationOrigin |
P135448
|
FINISHED |
| Object | Canton of St. Gallen |
—
|
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: Canton of St. Gallen | Statement: [SG, identifiesRegistrationOrigin, Canton of St. Gallen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesRegistrationOrigin Context triple: [SG, identifiesRegistrationOrigin, Canton of St. Gallen]
-
A.
identifiesRegistrationLocation
Indicates that an entity specifies the place or jurisdiction where a registration is or should be recorded.
-
B.
registrationOrigin
chosen
Indicates the source or context from which a registration event was initiated or created.
-
C.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
D.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
E.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65389145881909385f36f56cd250b |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.