Triple
T19831390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnard 1 |
E476467
|
entity |
| Predicate | isTypeOfRegion |
P137495
|
FINISHED |
| Object | low-mass star-forming dark cloud |
—
|
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: low-mass star-forming dark cloud | Statement: [Barnard 1, isTypeOfRegion, low-mass star-forming dark cloud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypeOfRegion Context triple: [Barnard 1, isTypeOfRegion, low-mass star-forming dark cloud]
-
A.
containsRegionType
Indicates that one region includes or encompasses another region of a specified type within its spatial or logical boundaries.
-
B.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
isFromRegion
Indicates that one entity originates from, is associated with, or belongs to a specified geographic region.
-
E.
typeOfRegionalization
Indicates the specific method or scheme by which a larger area is divided into regions or regional units.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656ce68b48190aa25b29d0b6ea021 |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:50 p.m.