Triple
T4618610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC 10 |
E100925
|
entity |
| Predicate | hasStarburstOrigin |
P3654
|
FINISHED |
| Object | possibly triggered by interaction or accretion |
—
|
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: possibly triggered by interaction or accretion | Statement: [IC 10, hasStarburstOrigin, possibly triggered by interaction or accretion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStarburstOrigin Context triple: [IC 10, hasStarburstOrigin, possibly triggered by interaction or accretion]
-
A.
hasBrightStar
Indicates that one entity possesses, contains, or is associated with a star characterized by high brightness.
-
B.
hasStarOn
Indicates that one entity bears or displays a star symbol positioned on another entity.
-
C.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
D.
containsAsterism
Indicates that one entity includes or encompasses an asterism (a recognizable pattern or grouping of stars) within its extent or definition.
-
E.
originalStar
Indicates that one entity is the initial or primary star from which another star or stellar object originates, is derived, or is otherwise based.
- 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.