Triple
T11468320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teapot Rock |
E271833
|
entity |
| Predicate | hasShapeResemblance |
P35666
|
FINISHED |
| Object | 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: teapot | Statement: [Teapot Rock, hasShapeResemblance, teapot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShapeResemblance Context triple: [Teapot Rock, hasShapeResemblance, teapot]
-
A.
resembles
chosen
Indicates that one entity is similar in appearance, form, or characteristics to another.
-
B.
hasDistinctiveShape
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
C.
hasSimilarityTo
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
D.
lessSimilarTo
Indicates that one entity is considered to share fewer similarities or a weaker resemblance with another entity compared to some reference or alternative.
-
E.
materiallySimilarTo
Indicates that two entities share substantially the same physical or material characteristics, composition, or properties, though they may not be exactly identical.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d82949e3688190b024a4980666c94f |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.