Triple
T19786951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SG |
E475293
|
entity |
| Predicate | plateSide |
P137328
|
FINISHED |
| Object | front and rear plates in Switzerland |
—
|
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: front and rear plates in Switzerland | Statement: [SG, plateSide, front and rear plates in Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plateSide Context triple: [SG, plateSide, front and rear plates in Switzerland]
-
A.
plate
Indicates that one entity serves as a plate or flat dish used to hold, support, or present another entity.
-
B.
plate3
Indicates that one entity is a third plate or dish associated with, supporting, or serving another entity in a given context.
-
C.
plateInterface
Indicates a physical or functional contact surface where one plate meets or connects with another component or plate.
-
D.
plateName
Indicates the name or label assigned to a specific plate.
-
E.
plateType
Indicates the specific category or style of plate associated with an item or context.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:49 p.m.