Triple
T20235935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 3918 |
E498147
|
entity |
| Predicate | dominantIon |
P116060
|
FINISHED |
| Object | doubly ionized oxygen (O III) |
—
|
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: doubly ionized oxygen (O III) | Statement: [NGC 3918, dominantIon, doubly ionized oxygen (O III)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantIon Context triple: [NGC 3918, dominantIon, doubly ionized oxygen (O III)]
-
A.
dominantComposition
Indicates that one entity is the primary or prevailing component, material, or element that makes up or characterizes another entity.
-
B.
mostAbundantIsotope
Indicates that one isotope of an element is identified as the most frequently occurring (highest natural abundance) among all its isotopes.
-
C.
dominantComplex
Indicates that one entity exerts primary control, influence, or prominence over another within a given context or system.
-
D.
dominantParticleType
chosen
Indicates that one particle type is the primary or most prevalent component within a given system, context, or interaction.
-
E.
dominatingFeature
Indicates that one feature stands out as the most prominent or influential characteristic in relation to others.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6716a5af0819095ea419a4d1f0d1d |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.