Triple
T5260080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monoceros Ring stellar stream |
E118800
|
entity |
| Predicate | hasLarge |
P60650
|
FINISHED |
| Object | angular extent on the sky |
—
|
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: angular extent on the sky | Statement: [Monoceros Ring stellar stream, hasLarge, angular extent on the sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLarge Context triple: [Monoceros Ring stellar stream, hasLarge, angular extent on the sky]
-
A.
hasLargeScale
chosen
Indicates that an entity operates, exists, or is implemented at a large or extensive scale relative to typical or baseline cases.
-
B.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
C.
hasLargePresenceIn
Indicates that an entity maintains a significant or dominant level of activity, influence, or representation within a specified location, domain, or context.
-
D.
largerThan
Indicates that one entity has a greater size, extent, or magnitude than another entity.
-
E.
hasLow
Indicates that an entity possesses a value, level, or amount of something that is below a defined or expected threshold.
- 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_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. |
Created at: March 20, 2026, 1:50 p.m.