Triple
T6623691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pisces Dwarf Galaxy |
E149740
|
entity |
| Predicate | hasHIExtent |
P68768
|
FINISHED |
| Object | more extended than stellar component |
—
|
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: more extended than stellar component | Statement: [Pisces Dwarf Galaxy, hasHIExtent, more extended than stellar component]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHIExtent Context triple: [Pisces Dwarf Galaxy, hasHIExtent, more extended than stellar component]
-
A.
containsSignificantHI
chosen
Indicates that something includes a substantial or noteworthy amount of high-intensity (HI) content, activity, or effect.
-
B.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
C.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
D.
hasHIIRegion
Indicates that an astronomical object contains or is associated with an H II (ionized hydrogen) region.
-
E.
hasExtendedStructure
Indicates that an entity possesses an additional or elongated structural component beyond its basic or standard form.
- 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:58 p.m.