Triple
T4994138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W5 star-forming region |
E112202
|
entity |
| Predicate | starFormationTriggeredBy |
P61363
|
FINISHED |
| Object | massive OB 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 OB stars | Statement: [W5 star-forming region, starFormationTriggeredBy, massive OB stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starFormationTriggeredBy Context triple: [W5 star-forming region, starFormationTriggeredBy, massive OB stars]
-
A.
starFormationActivity
Indicates the level or intensity of ongoing star formation occurring within an astronomical object or region.
-
B.
starFormationRate
Indicates the rate at which new stars are being formed within a given astronomical region or object over time.
-
C.
starFormationHistory
Indicates how the rate of star formation in an object or region has changed over time.
-
D.
hasStarFormationMode
Indicates the specific manner or process by which star formation occurs in a given astronomical system or region.
-
E.
stellarMass
Indicates the amount of mass an astronomical object has that is contained in its stars.
- 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd74713fc88190916c2b04cd2e677e |
completed | March 20, 2026, 4:23 p.m. |
Created at: March 20, 2026, 1:34 p.m.