Triple
T19086507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of the Kingdom of Saxony |
E467161
|
entity |
| Predicate | crancelinPosition |
P134323
|
FINISHED |
| Object | bendy sinister |
—
|
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: bendy sinister | Statement: [Coat of arms of the Kingdom of Saxony, crancelinPosition, bendy sinister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crancelinPosition Context triple: [Coat of arms of the Kingdom of Saxony, crancelinPosition, bendy sinister]
-
A.
rackPosition
Indicates the spatial placement or slot of an item within a rack or racking system.
-
B.
corePosition
Indicates that one entity occupies the central or primary position within another entity or structure.
-
C.
conePosition
Indicates the spatial position or placement of a cone relative to a reference frame or environment.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
cantonPosition
Indicates the relative placement or arrangement of a canton within a larger geographic or administrative 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e347ee288190a3e935ff89ca94aa |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.