Triple
T4619112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaus Media |
E100935
|
entity |
| Predicate | hasPositionInTeapot |
P6308
|
FINISHED |
| Object | forms part of the bow of the Teapot |
—
|
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: forms part of the bow of the Teapot | Statement: [Kaus Media, hasPositionInTeapot, forms part of the bow of the Teapot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionInTeapot Context triple: [Kaus Media, hasPositionInTeapot, forms part of the bow of the Teapot]
-
A.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
B.
hasTeeType
Indicates that an entity (typically a golf hole or course) is associated with a specific type or category of tee.
-
C.
estimatedTeaWeight
Indicates the quantified amount of tea that is approximated or predicted in weight rather than precisely measured.
-
D.
isToppedWith
Indicates that one entity serves as a topping placed on the surface of another entity.
-
E.
isAt
chosen
Indicates that one entity is located at or present in the place or position of another entity.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e3e6948190925e2cfad20dcc8c |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.