Triple
T16626936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanark Silver Bell |
E403970
|
entity |
| Predicate | hasObjectForm |
P169
|
FINISHED |
| Object | bell-shaped trophy |
—
|
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: bell-shaped trophy | Statement: [Lanark Silver Bell, hasObjectForm, bell-shaped trophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObjectForm Context triple: [Lanark Silver Bell, hasObjectForm, bell-shaped trophy]
-
A.
hasForm
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
B.
hasObject
Indicates that an entity is associated with or possesses a particular object as part of a relationship or action.
-
C.
hasFormFor
Indicates that one entity possesses or provides a specific form or document intended to be used by another entity or for a particular purpose.
-
D.
hasObjectSystem
Indicates that something is associated with, contains, or is part of a particular object system.
-
E.
hasObjectNotation
Indicates that an entity is represented or expressed using a specific object-based notation or symbolic format.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e375530ed081908337dc5c6360d733 |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.