Triple
T1335033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shimenawa |
E28727
|
entity |
| Predicate | placedAround |
P7850
|
FINISHED |
| Object | sumo wrestling ring |
—
|
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: sumo wrestling ring | Statement: [Shimenawa, placedAround, sumo wrestling ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placedAround Context triple: [Shimenawa, placedAround, sumo wrestling ring]
-
A.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
B.
surrounds
chosen
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
C.
createdAround
Indicates that something was brought into existence or produced approximately at a particular time or within an imprecise time period.
-
D.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
E.
placeHeld
Indicates that an entity occupies or is located at a specific place or position.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1eb119881909dd5fbf728d9e8ba |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.