Triple
T5260081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monoceros Ring stellar stream |
E118800
|
entity |
| Predicate | observedToward |
P62583
|
FINISHED |
| Object | constellation Monoceros |
—
|
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: constellation Monoceros | Statement: [Monoceros Ring stellar stream, observedToward, constellation Monoceros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedToward Context triple: [Monoceros Ring stellar stream, observedToward, constellation Monoceros]
-
A.
observationArc
Indicates a relationship where one entity serves as an observational link or span over which another entity is monitored, tracked, or measured across a period or range.
-
B.
dstObserved
Indicates that an entity has been observed, detected, or recorded as the destination of another entity or action.
-
C.
observedVia
Indicates that something is perceived, detected, or measured through a particular medium, instrument, method, or channel.
-
D.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
E.
observedAt
Indicates that an entity was recorded or noticed at a specific time or place.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:50 p.m.