Triple
T18771143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamaeleon molecular clouds |
E459018
|
entity |
| Predicate | hasExtinction |
P133475
|
FINISHED |
| Object | high visual extinction regions |
—
|
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: high visual extinction regions | Statement: [Chamaeleon molecular clouds, hasExtinction, high visual extinction regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExtinction Context triple: [Chamaeleon molecular clouds, hasExtinction, high visual extinction regions]
-
A.
hasExtinctSpecies
Indicates that at least one species associated with the subject entity is no longer extant (i.e., has gone extinct).
-
B.
hasExtinctMembers
Indicates that at least some members of the referenced group, class, or category are no longer living or existing.
-
C.
extinctUpon
Indicates that one entity ceases to exist or becomes extinct as a direct consequence of, or at the point of, another specified event or condition.
-
D.
hasExtinctSubspecies
Indicates that an entity has at least one subspecies that is extinct.
-
E.
extinctionPeriod
Indicates the time span during which an entity ceases to exist or is considered extinct.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59335a01881908731371be1e27a6b |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:52 a.m.