Triple
T19931870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S106 nebula |
E479072
|
entity |
| Predicate | illuminatedBy |
P38235
|
FINISHED |
| Object | S106 IR |
—
|
NE NERFINISHED |
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: S106 IR | Statement: [S106 nebula, illuminatedBy, S106 IR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: S106 IR Context triple: [S106 nebula, illuminatedBy, S106 IR]
-
A.
S106 IR
chosen
S106 IR is a massive young stellar object deeply embedded in the S106 nebula, whose intense radiation and stellar winds carve the nebula’s characteristic bipolar structure.
-
B.
S 106
S 106 is a bipolar emission nebula in the constellation Cygnus, notable for its hourglass shape and active star-forming region surrounding a massive young star.
-
C.
IR-20
IR-20 is the ISO 3166-2 subdivision code assigned to Iran’s Semnan Province.
-
D.
S-102
S-102 is an IHO S-100 series standard that defines high-resolution bathymetric surface data for use in modern electronic navigation and marine applications.
-
E.
S-101
S-101 is the International Hydrographic Organization’s modern electronic navigational chart standard designed to support next-generation marine navigation systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a13ebc08190a583aa4c5e9f6648 |
completed | April 20, 2026, 4:53 p.m. |
Created at: April 10, 2026, 1:53 p.m.