Triple
T20235932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 3918 |
E498147
|
entity |
| Predicate | ejectionOrigin |
P139344
|
FINISHED |
| Object | outer layers of a dying star |
—
|
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: outer layers of a dying star | Statement: [NGC 3918, ejectionOrigin, outer layers of a dying star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ejectionOrigin Context triple: [NGC 3918, ejectionOrigin, outer layers of a dying star]
-
A.
ejection
Indicates the forceful expulsion or removal of one entity from another entity, system, or location.
-
B.
ejectionRecord
Indicates that there is a recorded instance of an entity being expelled, removed, or discharged from a place, system, or context.
-
C.
ejectorType
Indicates the specific kind or category of ejector mechanism associated with an entity or system.
-
D.
typicalEjectedMass
Indicates the characteristic amount of mass that is usually expelled from a system or object during an ejection event.
-
E.
catapultOrigin
Indicates the original source or starting point from which something is launched or propelled, as by a catapult.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:40 p.m.