Triple
T19182824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambda Sagittarii |
E469618
|
entity |
| Predicate | marksAsterismFeature |
P99152
|
FINISHED |
| Object | top 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: top of the Teapot | Statement: [Lambda Sagittarii, marksAsterismFeature, top of the Teapot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksAsterismFeature Context triple: [Lambda Sagittarii, marksAsterismFeature, top of the Teapot]
-
A.
marksAstronomicalEvent
Indicates that one entity serves as a sign, boundary, or reference point denoting the occurrence or timing of an astronomical event.
-
B.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
C.
markingFeature
chosen
Indicates a feature that serves as a distinguishing mark or identifier associated with an entity.
-
D.
containsAsterism
Indicates that one entity includes or encompasses an asterism (a recognizable pattern or grouping of stars) within its extent or definition.
-
E.
hasAstronomicalFeature
Indicates that an entity possesses, contains, or is characterized by a specific astronomical feature (such as a star, planet, crater, or other celestial structure).
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f61e1c248190ba9e220c1be61ef8 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.