Triple
T18843000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ε Sagittarii |
E460842
|
entity |
| Predicate | positionInTeapot |
P133147
|
FINISHED |
| Object | southern 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: southern bow of the Teapot | Statement: [ε Sagittarii, positionInTeapot, southern bow of the Teapot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTeapot Context triple: [ε Sagittarii, positionInTeapot, southern bow of the Teapot]
-
A.
partOfCup
Indicates that one entity is a physical component or constituent belonging to a cup.
-
B.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
C.
domesticCupHierarchyPosition
Indicates the relative ranking or level of a team or participant within the structure or tiers of a domestic cup competition.
-
D.
positionOnSubstance
Indicates that one entity is located on the surface of, or supported by, another entity that is treated as a substance or material.
-
E.
ingredientPositioning
Indicates the spatial or ordered arrangement of ingredients relative to one another within a composition or structure.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8eb32548190b2313e877f6ff179 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:56 a.m.