Triple
T20327504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1E 0102.2-7219 |
E492377
|
entity |
| Predicate | hasProgenitorType |
P139719
|
FINISHED |
| Object | massive star |
—
|
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: massive star | Statement: [1E 0102.2-7219, hasProgenitorType, massive star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgenitorType Context triple: [1E 0102.2-7219, hasProgenitorType, massive star]
-
A.
hasAncestralType
Indicates that one type is derived from, or originates from, another more primitive or original type in an inheritance or lineage hierarchy.
-
B.
hasPredecessorType
Indicates that one type is derived from, follows, or is based on another earlier or more fundamental type in a sequence or hierarchy.
-
C.
hasTypeGenus
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
D.
typeOfAncestor
Indicates that one entity is an ancestor (of any generational distance) of another entity.
-
E.
progenitorOf
Indicates that one entity is the direct biological or ancestral source (parent or originator) of another entity.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e513608190b70527cd9f4d5da3 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:21 a.m.