Triple
T4618596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC 10 |
E100925
|
entity |
| Predicate | dustContent |
P27659
|
FINISHED |
| Object | relatively high internal extinction |
—
|
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: relatively high internal extinction | Statement: [IC 10, dustContent, relatively high internal extinction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dustContent Context triple: [IC 10, dustContent, relatively high internal extinction]
-
A.
debrisDiskDustContent
chosen
Indicates the amount or characteristics of dust present within a debris disk surrounding an astronomical object.
-
B.
GCContent
Indicates the proportion of guanine (G) and cytosine (C) bases relative to the total nucleotide content in a DNA or RNA sequence.
-
C.
fiberContent
Indicates that one entity specifies the amount or presence of dietary fiber contained in another entity.
-
D.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
E.
distributesContentTo
Indicates that one entity delivers or makes content available to another entity or set of entities.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.