Triple
T5225875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 30 Doradus |
E117983
|
entity |
| Predicate | ionizationSource |
P58484
|
FINISHED |
| Object | massive young stars |
—
|
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 young stars | Statement: [30 Doradus, ionizationSource, massive young stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ionizationSource Context triple: [30 Doradus, ionizationSource, massive young stars]
-
A.
ionizingSource
chosen
Indicates that the subject acts as a source that produces or emits ionizing radiation affecting the object.
-
B.
ionizes
Indicates that one entity causes another entity to gain or lose electrons, thereby converting it into an ion.
-
C.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
D.
hasIonizationState
Indicates the specific ionization state or charge level that an entity (such as an atom or molecule) possesses.
-
E.
usesIonType
Indicates that one entity employs or operates using a specific type of ion in its function or process.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adc9be081909903b9f844c3d146 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.